[FATAL] [DBT-10503] Template file is not specified

-
I faced an error [FATAL] [DBT-10503] Template file is not specified and terminated operation when I was going to create 12c instance in silent mode .

 

ERROR:

[FATAL] [DBT-10503] Template file is not specified.

 

REASON:

This is due to the you are not set the “templateName” in response file.

 

SOLUTION:

Set templateName=General_Purpose.dbc and execute the dbca again

 

ACTION:

1.       Open the dbca.rsp and set templateName as General_Purpose.dbc
2.       Save the dbca.rsp
3.       Execute the instance create statement again (dbca)



Comments

Post a Comment

Popular posts from this blog

Enabling Transparent Data Encryption (TDE) in Oracle RAC on ODA with Data Guard – The Correct and Secure Approach

-
Image
Transparent Data Encryption (TDE) is a critical security feature in Oracle Database that protects sensitive data at rest by encrypting datafiles, tablespaces, or specific columns. In modern enterprise environments especially Oracle RAC deployments on Oracle Database Appliance (ODA) with Data Guard TDE implementation must be done carefully to avoid service disruption, Data Guard lag, or wallet inconsistencies. This article walks through the correct, production-safe method to enable TDE with Auto-Login Wallet while ensuring: ·                No exposure of sensitive credentials ·                Consistency across RAC nodes ·                Seamless synchronization with the physical standby   ⚠️ Important: This guide assumes Oracle Database 19c on ODA, RAC Primary, ...
Read more

Resolving ORA-10635 and ORA-39171 Errors During BLOB Tablespace Maintenance

-
Recently, I came across an interesting situation while performing a space management task on one of our databases. The challenge involved a table that contained BLOB data distributed across multiple tablespaces . What seemed like a simple shrink operation ended up turning into a deeper learning experience that I’d like to share. 🧩 Background In this environment, the main table BINARY_ARCHIVE was stored in the MAIN_DATA tablespace. Its BLOB segment was placed separately in the ATTACHMENTS_DATA tablespace to improve performance and manage large object storage efficiently. Additionally, another table called BINARY_OBJECT_LINK maintained a foreign key reference to the BLOB data and resided in the LINK_DATA tablespace. When I attempted to reclaim space from the BLOB segment using the SHRINK SPACE command, Oracle returned the following error. ⚠️ The Error ORA -10635 : Invalid segment or tablespace type 10635. 00000 - " Invalid segment or tablespace type " *Ca...
Read more