Skip to main content

Posts

Showing posts from May, 2017

ORA-02291: integrity constraint violated - parent key not found

“Error: ORA-02291: integrity constraint violated - parent key not found” Reason:    A Primary key does not have the same value as the foreign key. We will discuss it in detail later in this article. Action:   For  ORA-02291: integrity constraint violated - parent key not found  You may either delete the foreign key or the matching primary key can be added. In either way, you may try to get this error corrected. Let's understand more about ORA-02291: integrity constraint violated - parent key not found? The Oracle software brought us the strength by which multiple tables in the database can pass on information so efficiently. Not only this, there are numerous devices in this software which enables access to and sourcing data from multiple tables. You can easily execute complicated database issues without an unusual uncertainty by creating statements with the fantastic characteristic of this software. Realistically, if we talk about user or database no one is perf...

ORA-01033: ORACLE initialization or shutdown in progress

ORA-01033: ORACLE initialization or shutdown in progress Cause:  You are trying to access oracle database while  database is either starting up or shuting down (ORA-01033: ORACLE initialization or shutdown in progress). Action: For ORA-01033: ORACLE initialization or shutdown in progress you need to wait for some time. Then retry the operation again (connect after some time) to check if ORA-01033: ORACLE initialization or shutdown in progress is there or not. What is ORA-01033: ORACLE initialization or shutdown in progress? This is very common error and not occurs much. But you must have some idea if you face ORA-01033: ORACLE initialization or shutdown in progress occurs. As we know We can only set database to  Shutdown or startup using SYSDBA privileges. So you must have SYSDBA privileges to troubleshoot. I suggest  to  wait for 5mins because may be your DBA has shutdown the Database and it's in progress.Or if you are a DBA then check the status of databa...

ORA-12714 invalid national character set specified

Error: ORA-12714 ORA-12714  invalid national character set specified  ORA-12714 invalid national character set specified  is very common error and related to database parameters and sessions parameters. Cause  Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Check your NLS_NCHAR_CHARACTERSET which is set using: select value from NLS_DATABASE_PARAMETERS where parameter = 'NLS_NCHAR_CHARACTERSET'; it should return UTF8 Or AL16UTF16 Action Ensure that the specified national character set is valid Please aware that at session level, some parameters could be different. If you want to be sure, compare the results of: select * from nls_database_parameters; with: select * from nls_session_parameters; Please find the below information:-     Bug No :- 2834295  Cause :-  declaring cursor for a function that returns a table of NVARCHAR2   Affects below products : Product ( Component ) Oracle Server (Rdbms) ...