Tuesday, December 17, 2019

How to resolve ORA-38824: A CREATE OR REPLACE command may not change the EDITIONABLE property of an existing object.

From Oracle version 12c onwards: -

Initially It seems the problem is related to Editioning feature of the object in the db is not enable or the schema user is not created with edition enable.
However it could be a related to container and non container DB.
This issue will not come where CDB=NO
In those cases where CDB=YES it will come and seems to be a bug.

Just Check:

SQL> select name,dbid,con_dbid,cdb,con_id from v$database;


NAME            DBID   CON_DBID CDB     CON_ID
--------- ---------- ---------- --- ----------
CDB1      1000678150 1000358150 YES          0


If CDB is yes means its a container DB and installer will fail.

 SQL> select name,dbid,con_dbid,cdb,con_id from v$database;

 NAME            DBID   CON_DBID CDB     CON_ID
--------- ---------- ---------- --- ----------
ORCLXYZ  74410566 2774410566 NO           0


If CDB is NO issue will not come.

How to resolve ORA-01400: cannot insert NULL into ("ABUSER"."DOMAINS"."ID")

How to resolve ORA-01400: cannot insert NULL into ("ABUSER"."DOMAINS"."ID")
[Failed SQL: INSERT INTO ABUSER.Domains (Name, RowVersion) VALUES ('Default Domain', '1')]

If this issue is coming before Oracle 12c(11g) then it could be an issue with the sequence.
Try to create the sequnce on the right column.

Post or from Oracle 12c first check the alert log,it will throw an exception of creating temp tablespace size.
Unable to extend temp tablespace...
Initially It seems the problem is related to Domain index.
However it could be a related to container and non container DB.
This issue will not come where CDB=NO
In those cases where CDB=YES it will come and seems to be a bug.

Just Check:

SQL> select name,dbid,con_dbid,cdb,con_id from v$database;


NAME            DBID   CON_DBID CDB     CON_ID
--------- ---------- ---------- --- ----------
CDB1      1000678150 1000358150 YES          0


If CDB is yes means its a container DB and installer will fail.

 SQL> select name,dbid,con_dbid,cdb,con_id from v$database;

 NAME            DBID   CON_DBID CDB     CON_ID
--------- ---------- ---------- --- ----------
ORCLXYZ  74410566 2774410566 NO           0


If CDB is NO issue will not come.


Friday, August 23, 2019

ERROR in alert log: Shared memory area is accessible to instance startup process prior to instance startup operation

Applicable to Oracle DB  Release 12.1.0.2.0.

Developer when connecting to a PDB service through SQLdeveloper may see the error startup shutdown in progress after restart of the Database in Oracle 12c or afterwards.

Issue applicable if we don't save the state of the DB.

Usually from Oracle 12c if we don't save the state of a PDB database after the restart PDB may not come up to the same state.

In that case we may face this issue.

Resolution:

SQL> connect to the DB.


Connected.

Check the status of the PDBs.

SQL> select con_id, name, open_mode, total_size from v$pdbs;

    CON_ID NAME                           OPEN_MODE  TOTAL_SIZE
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       READ ONLY   838860800
         3 PDBCR                          MOUNTED             0

SQL> alter pluggable database PDB$SEED CLOSE IMMEDIATE;
alter pluggable database PDB$SEED CLOSE IMMEDIATE
                         *
ERROR at line 1:
ORA-65017: seed pluggable database may not be dropped or altered

Open the PDB database

SQL> alter pluggable database PDBCR open;

Pluggable database altered.

Again check the PDB status

SQL> select con_id, name, open_mode, total_size from v$pdbs;

    CON_ID NAME                           OPEN_MODE  TOTAL_SIZE
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       READ ONLY   838860800
         3 PDBCR                          READ WRITE 4229955584