OIM/OAM 12c RCU Creation failed for Oracle Database 12c

Issue:

When we run RCU utility to create OIM/OAM Schemas, the following error is encountered
Mon Jul 24 13:36:02.696 UTC 2018 ERROR assistants.rcu.backend.task.PrereqTask: oracle.sysman.assistants.rcu.backend.task.PrereqTask::execute: Prereq Evaluation Failed
oracle.sysman.assistants.rcu.backend.validation.PrereqException:
ERROR – RCU-6083 Prerequisite check failed for selected component:
CAUSE – RCU-6083 Prerequisite check failed for selected component.
ACTION – RCU-6083 Refer to the RCU logs for additional details. Make sure that the prerequisite requirements are met.
Refer to RCU log at /tmp/RCU2018-07-24_13-30_1931354565/logs/rcu.log for details.
at oracle.sysman.assistants.rcu.backend.validation.PrereqEvaluator.executePrereqTask(PrereqEvaluator.java:713)
at oracle.sysman.assistants.rcu.backend.task.PrereqTask.execute(PrereqTask.java:68)
at oracle.sysman.assistants.rcu.backend.task.ActualTask.run(TaskRunner.java:346)
at java.lang.Thread.run(Thread.java:748)
Mon Jul 24 13:36:02.697 UTC 2018 ERROR assistants.rcu.backend.task.ActualTask: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: RCU Operation Failed
oracle.sysman.assistants.common.task.TaskExecutionException:
ERROR – RCU-6083 Prerequisite check failed for selected component:
CAUSE – RCU-6083 Prerequisite check failed for selected component.
ACTION – RCU-6083 Refer to the RCU logs for additional details. Make sure that the prerequisite requirements are met.
Refer to RCU log at /tmp/RCU2018-09-24_13-30_1931354565/logs/rcu.log for details.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Error: Views/Synonyms required for XA transaction support are missing in this Database 12c.
These views/synonyms are required by the OIM Schema.
Action: Refer Oracle Database Administrator’s Guide to install XA transaction recovery views/synonyms using the script xaview.sql. Contact your DBA.
For Database12c CDB config: execute xaview.sql from PDB SYS user
For Database12c NON-CDB config: execute xaview.sql from CDB SYS user

Resolution:

Step 1
Login to your database as sys or any other user with sysdba privileges and run below two scripts

@$ORACLE_HOME/javavm/install/initxa.sql
@$ORACLE_HOME/rdbms/admin/xaview.sql

Step 2
Along with the above views, make sure following parameters are tuned as per Oracle's recommendation
PROCESSES (min > 300)
NLS_LENGTH_SEMANTICS (BYTE)
SHARED_POOL_SIZE ( min > 200MB)
SGA_MAX_SIZE (min > 200MB)
DB_BLOCK_SIZE (min > 8k)
OPEN_CURSORS (min > 1000)

ORA-01078: failure in processing system parameters LRM-00109: could not open parameter file - Fixed

Requirement - When starting up database following error occurs:

SQL> startup
ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file ‘/opt/oracle/product/11.2.0/dbhome_1/dbs/inittest01.ora’

I have faced this problem, while setting up an new image of VMware. I am starting server and I got this error.
What does this mean –

Reason-
Database start using spfile (Default)
In Unix default path is $ORACLE_HOME/dbs
If spfile is not present it looks for pfile at same path. If pfile is also not present it will give above message.

Implementation -
If you have spfile then you can copy default values from spfile to pfile and create pfile. But what if you don’t have spfile
You have to create an pfile

How to create pfile –

When database starts it writes list of non default parameters in alert log files. We can use these values to create a pfile and start the database.

Find your Alert log file and open it, this is Database Management Software Oracle 11g
Here you will see entry like this:

processes = 150
sga_target = 512M
control_files = “/opt/oracle/test01/dbs/control01.ctl”
control_files = “/opt/oracle/test01/dbs/control02.ctl”
control_files = “/opt/oracle/test01/dbs/control03.ctl”
db_block_size = 8192
compatible = “10.2.0.1.0”
log_archive_dest_1 = “LOCATION=/opt/oracle/test01/archive”
log_archive_dest_state_1 = “ENABLE”
log_archive_format = “%t_%s_%r.dbf”
log_archive_max_processes= 10
log_checkpoint_interval = 9999
log_checkpoint_timeout = 0
db_file_multiblock_read_count= 16
db_recovery_file_dest = “/opt/oracle/test01/flash_recovery_area”
db_recovery_file_dest_size= 2G
undo_management = “AUTO”
undo_tablespace = “UNDOTBS1”
remote_login_passwordfile= “EXCLUSIVE”
db_domain = “agilis.com”
job_queue_processes = 32
core_dump_dest = “/opt/oracle/test01/diag/cdump”
audit_file_dest = “/opt/oracle/test01/adump”
open_links = 10
db_name = “test01”
open_cursors = 500
optimizer_index_cost_adj = 20
optimizer_index_caching = 90
pga_aggregate_target = 128M
diagnostic_dest = “/opt/oracle/test01/diag”

Create pfile using these values:
$ cd /opt/oracle/product/11.2.0/dbhome_1/dbs/
vi inittest01.ora

Copy non default parameter values from alert log in this file and save it. This is your pfile,
Start the database using this pfile

Start the Database using Pfile:

[oracle@ dbs]$ export ORACLE_SID=test01
 [oracle@ dbs]$ sqlplus sys as sysdba
 SQL*Plus: Release 11.2.0.2.0 Production on Fri Jun 24 15:53:16 2011
 Copyright (c) 1982, 2010, Oracle. All rights reserved.
 Enter password:
 Connected to an idle instance.
 SQL> startup pfile=’$ORACLE_HOME/dbs/inittest01.ora’
ORACLE instance started.
 Total System Global Area 534462464 bytes
 Fixed Size 2228200 bytes
 Variable Size 163577880 bytes
 Database Buffers 360710144 bytes
 Redo Buffers 7946240 bytes
 Database mounted.
 Database opened.
 SQL>

Create spfile from pfile:

SQL> create spfile from pfile=’$ORACLE_HOME/dbs/inittest01.ora’;
File created.

Shutdown the database and restart it will use spfile (Default) and problem is solved.

ORA-00106: cannot startup/shutdown database when connected to a dispatcher

Problem Description

We are running a multi-threaded server and are trying to shutdown the database. But it fails through below message

ORA-00106: cannot startup/shutdown database when connected to a dispatcher

In simplest, ORA-00106 means following according to oracle documentation

Cause: An attempt was made to startup/shutdown database when connected to a shared server via a dispatcher.
Action: Re-connect as user INTERNAL without going through the dispatcher.
For most cases, this can be done by connect to INTERNAL without specifying a network connect string

Cause of the Problem
The problem happened because you are trying to shutdown the database while connected to a shared server process.
Because you cannot startup or shutdown a database while connected to a shared server process via a dispatcher.
To shutdown or startup a database you must connect via a dedicated server process.

Solution of the Problem

In order to startup/shutdown a database, you must connect via a dedicated server process and not a shared process.
If you are connecting to database server through TNS entry then add the following entry to your tnsnames.ora file in the address_list section:

(SERVER=DEDICATED)

Example of a TNS entry that establish a dedicated connection:

 service_name=
      (DESCRIPTION =
          (ADDRESS_LIST =
             (ADDRESS =
              (PROTOCOL = PROTOCOL_NAME)
                (Host = server_name)
                (Port = port_number)
             )
          )
         (CONNECT_DATA =
             (SID = sid_name)
             (SERVER=DEDICATED)
         )
       )

Another solution is login to the server and issue startup/shutdown from that computer by connecting as sysdba without any TNS entry

Catuppst.sql fails with "GGUSER.DDLREPLICATION" does not exist after upgrading the database

ORA-00604: error occurred at recursive SQL level 1
ORA-04045: errors during recompilation/revalidation of GGUSER.DDLREPLICATION
ORA-04067: not executed, package body "GGUSER.DDLREPLICATION" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "GGUSER.DDLREPLICATION"
ORA-06512: at line 1027
ORA-04067: not executed, package body "GGUSER.DDLREPLICATION" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "GGUSER.DDLREPLICATION"

Followed by this, utlrp.sql would also result the same error.

Database components "Oracle XML Database" and "Oracle Database Packages and T" (CATPROC) will be in INVALID state.

Solution:

According to below Metalink note

ORA-03113: During an Upgrade while Running Catuppst.sql ORA-6508 "GGUSER.DDLREPLICATION" in alert.log (Doc ID 1506156.1)

we need to disable the system trigger that was enable for DDL replication during Golden gate setup.

SQL> alter trigger sys.GGS_DDL_TRIGGER_BEFORE disable;

Now, re run catuppst.sql and utlrp.sql

Once this goes successfully, enable the trigger again.

SQL> alter trigger sys.GGS_DDL_TRIGGER_BEFORE enable;

How to resolve ORA-24247: network access denied by access control list (ACL)

sqlplus sys as sysdba

SQL>SELECT * FROM dba_network_acl_privileges;

SQL>select * from dba_network_acls;

SQL>GRANT EXECUTE ON UTL_TCP TO scott;
SQL>GRANT EXECUTE ON UTL_SMTP TO scott;
SQL>GRANT EXECUTE ON UTL_MAIL TO scott;

Assign Privileges to already present ACL

BEGIN
DBMS_NETWORK_ACL_ADMIN.ADD_PRIVILEGE(
 acl => 'acl_for_accd.xml',
principal => 'scott',
is_grant => true,
privilege => 'connect');
COMMIT;
END;
/

BEGIN
dbms_network_acl_admin.assign_acl (
acl => 'acl_for_accd.xml',
host => 'IP Address of Email Server',
lower_port => 25,
upper_port => 80
);
COMMIT;
END;
/

OR

BEGIN
dbms_network_acl_admin.assign_acl (
acl => 'acl_for_accd.xml',
host => '*',
);
COMMIT;
END;
/

Oracle 12c SEC_CASE_SENSITIVE_LOGON and ORA-01017

The init.ora/spfile parameter SEC_CASE_SENSITIVE_LOGON got deprecated since Oracle Database 12.1.0.1
This means, we don’t do any further developments to it, you shouldn’t change it from its default TRUE and if you still do you’ll receive a nice warning during STARTUP of your database:

SQL> alter system set sec_case_sensitive_logon=false scope=spfile;
System altered.

SQL> startup force
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.

Recently a user asked me if we’d changed the behavior of this parameter in Oracle Database 12c Release 2 as he receives now an ORA-01017: Invalid username or password error when having SEC_CASE_SENSITIVE_LOGON=FALSE with every user except SYSDBAs

In which situations may you receive an ORA-01017?

This is outlined in the Oracle 12.1 documentation already:
•Ensure that the SEC_CASE_SENSITIVE_LOGON parameter is not set to FALSE if the SQLNET.ALLOWED_LOGON_VERSION_SERVER parameter is set to 12 or 12a
This is because the more secure password versions used for this mode only support case-sensitive password checking.
For compatibility reasons, Oracle Database does not prevent the use of FALSE for SEC_CASE_SENSITIVE_LOGON when SQLNET.ALLOWED_LOGON_VERSION_SERVER is set to 12 or 12a
Setting SEC_CASE_SENSITIVE_LOGON to FALSE when SQLNET.ALLOWED_LOGON_VERSION_SERVER is set to 12 or 12a causes all accounts to become inaccessible.

The key is the sqlnet.ora parameter SQLNET.ALLOWED_LOGON_VERSION_SERVER and here’s the difference between Oracle Database 12.1 and Oracle Database 12.2:
•Oracle Database 12.1: SQLNET.ALLOWED_LOGON_VERSION_SERVER defaults to 11 out of the box
•Oracle Database 12.2: SQLNET.ALLOWED_LOGON_VERSION_SERVER defaults to 12 out of the box

Behavior difference Oracle 12.1 vs Oracle 12.2

See this simple example after switching SEC_CASE_SENSITIVE_LOGON=FALSE in both databases (as shown above):
•Oracle Database 12.1.0.2:

SQL> alter user system identified by oracle;
User altered.

SQL> connect system/oracle
Connected.

•Oracle Database 12.2.0.1:

SQL> alter user system identified by oracle;
User altered.

SQL> connect system/oracle
ERROR:
ORA-01017: invalid username/password; logon denied

Warning: You are no longer connected to ORACLE

How to workaround the ORA-01017?

First of all you need to edit your sqlnet.ora adding (or lowering) the parameter SQLNET.ALLOWED_LOGON_VERSION_SERVER to a value below 12
But if you try to connect directly after restarting your listener you will receive the same ORA-01017 again
The secret is mentioned in the above documentation link as well, you will have to recreate the user’s password if you need the logon process to work as it did work before Oracle Database 12.2

sqlnet.ora
# sqlnet.ora Network Configuration File: /u01/app/oracle/product/12.2.0.1/network/admin/sqlnet.ora
# Generated by Oracle configuration tools.

NAMES.DIRECTORY_PATH= (TNSNAMES, ONAMES, HOSTNAME)
SQLNET.ALLOWED_LOGON_VERSION_SERVER=11

Check in DBA_USERS

SQL> select username, password_versions 
from DBA_USERS 
where username='SYSTEM';

USERNAME      PASSWORD_VERSIONS
------------- ---------------------
SYSTEM        11G 12C

There’s no “10G” mentioned. This will prevent the connection.

Solution: You will have to specify the password again respective ALTER the user(s):

SQL> alter user system identified by oracle;
User altered.

SQL> select username, password_versions 
from DBA_USERS 
where username='SYSTEM';

USERNAME       PASSWORD_VERSIONS
-------------- ----------------------
SYSTEM         10G 11G 12C

SQL> connect system/oracle
Connected.

ODBC error: SQLSTATE 37000 native database error 4060

Now, when you go to start the extract/replicat, you may get the following error:
ERROR OGG-00551 Database operation failed: Couldn’t connect to [ dns ]. ODBC error: SQLSTATE 37000 native database error 4060. [Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database “db_name” requested by the login. The login failed.
The error message is a little bit misleading. It tells you that the process cannot connect to the database which you were able to connect to from the GGSCI command prompt with no issue.

Why is this?
The issue lies in the fact that the manager (MGR) process is running as a service and does not have the correct permissions to access the database from the service.

In searching MOS for this error, I was found Note ID: 1633138.1.
In this note, notice that this issue is known as of Oracle GoldenGate version 12.1.2.x.x. The note also provides you a fix to this issue. In simple terms, since the manager process is running as a service; additional permissions have to be granted to manger.

To grant the SYSADMIN privilege for the manager process follow the below sequence of steps (on windows after all):
1. Manager is installed as service:
Open SQL Server Management studio -> Security ->login>select NT AUTHORITY\SYSTEM ->Right Click -> Properties–>Server Role –>Enable sysadmin role
2. ggsci>stop mgr
3. ggsci>start mgr
4. ggsci>start extract <extract-name>

After granting the sysadmin role, the extract will start.

SQLPLUS.EXE counterprocess error =1392

Resolution

1. Uninstall Oracle product
2. Install JAVA
3. Set Environmental Variables for JAVA_HOME and JRE_HOME
4. Install Oracle Product again

ORA-19905: log_archive_format must contain %s, %t and %r

ORA-19905:- this error generate due to incorrect Archive log format in oracle Release 12.1.0.0.1.0.

Problem:-
 SQL> startup;
 ORA-19905: log_archive_format must contain %s, %t and %r

 SQL> startup mount;
 ORA-19905: log_archive_format must contain %s, %t and %r

Solution:
Also solution is given in metalink note 283507.1

  - create pfile from spfile using below command

 SQL> create pfile from spfile;

 File created.

 - got to oracle pfile location and edit the 'log_archive_format' parameter

 [oracle@dns1 prmdb]$ cd /u01/app/oracle/product/12.1.0.0/db_1/dbs/

 [oracle@dns1 dbs]$ vi  initprmdb.ora

 -----------------before update----------------------------------

 prmdb.__db_cache_size=1979711488
 prmdb.__java_pool_size=16777216
 prmdb.__large_pool_size=16777216
 prmdb.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
 prmdb.__pga_aggregate_target=2097152000
 prmdb.__sga_target=3154116608
 prmdb.__shared_io_pool_size=0
 prmdb.__shared_pool_size=1073741824
 prmdb.__streams_pool_size=33554432
 *.audit_file_dest='/u01/app/oracle/admin/prmdb/adump'
 *.audit_trail='db'
 *.compatible='12.1.0.0.0.0'
 *.control_files='/u01/app/oracle/oradata/prmdb/control01.ctl','/u01/app/oracle/oradata/prmdb/control02.ctl'
 *.cursor_sharing='FORCE'
 *.db_block_size=8192
 *.db_domain=''
 *.db_name='prmdb'
 *.diagnostic_dest='/u01/app/oracle'
 *.dispatchers='(PROTOCOL=TCP) (SERVICE=prmdbXDB)'
*.log_archive_dest_1='LOCATION=/u01/Archive'
*.log_archive_format='arch_%t_%s'
 *.memory_max_target=0
 *.memory_target=0
 *.open_cursors=1500
 *.pga_aggregate_target=2097152000
 *.processes=1000
 *.remote_login_passwordfile='EXCLUSIVE'
 *.session_cached_cursors=1000
 *.sga_target=3154116608
 *.timed_statistics=TRUE
 *.undo_tablespace='UNDOTBS1'

--------------------After update------------------------------------
 prmdb.__db_cache_size=1979711488
 prmdb.__java_pool_size=16777216
 prmdb.__large_pool_size=16777216
 prmdb.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
 prmdb.__pga_aggregate_target=2097152000
 prmdb.__sga_target=3154116608
 prmdb.__shared_io_pool_size=0
 prmdb.__shared_pool_size=1073741824
 prmdb.__streams_pool_size=33554432
 *.audit_file_dest='/u01/app/oracle/admin/prmdb/adump'
 *.audit_trail='db'
 *.compatible='12.1.0.0.0.0'
 *.control_files='/u01/app/oracle/oradata/prmdb/control01.ctl','/u01/app/oracle/oradata/prmdb/control02.ctl'
 *.cursor_sharing='FORCE'
 *.db_block_size=8192
 *.db_domain=''
 *.db_name='prmdb'
 *.diagnostic_dest='/u01/app/oracle'
 *.dispatchers='(PROTOCOL=TCP) (SERVICE=prmdbXDB)'
*.log_archive_dest_1='LOCATION=/u01/Archive'
*.log_archive_format='arch_%r_%t_%s'
 *.memory_max_target=0
 *.memory_target=0
 *.open_cursors=1500
 *.pga_aggregate_target=2097152000
 *.processes=1000
 *.remote_login_passwordfile='EXCLUSIVE'
 *.session_cached_cursors=1000
 *.sga_target=3154116608
 *.timed_statistics=TRUE
 *.undo_tablespace='UNDOTBS1'

 [oracle@dns1 dbs]$ sqlplus

 SQL*Plus: Release 12.1.0.0.1.0 Production on Mon Mar 3 01:32:10 2014

 Copyright (c) 1982, 2009, Oracle.  All rights reserved.

 Enter user-name: /as sysdba
 Connected to an idle instance.

SQL>create spfile from pfile;
File created.

 SQL> startup
 ORACLE instance started.

 Total System Global Area 5261217792 bytes
 Fixed Size                  2222560 bytes
 Variable Size            3271558688 bytes
 Database Buffers         1979711488 bytes
 Redo Buffers                7725056 bytes
 Database mounted.
 Database opened.

 SQL> archive log list;
 Database log mode              Archive Mode
 Automatic archival             Enabled
 Archive destination            /u01/Archive
 Oldest online log sequence     760
 Next log sequence to archive   762
 Current log sequence           762

 SQL> alter system switch logfile;
 System altered.

 SQL> /
 System altered.

 SQL> archive log list;
 Database log mode              Archive Mode
 Automatic archival             Enabled
 Archive destination            /u01/Archive

ORA - 04063: package body "SYS.DBMS_REGISTRY_SYS" has errors while running utlrp...

SQL>@utlrp.sql
*
ERROR at line 1:
ORA-04063: package body "SYS.DBMS_REGISTRY_SYS" has errors

BEGIN dbms_registry_sys.validate_components; END;

*
ERROR at line 1:
ORA-04063: package body "SYS.DBMS_REGISTRY_SYS" has errors
ORA-06508: PL/SQL: could not find program unit being called:
"SYS.DBMS_REGISTRY_SYS"
ORA-06512: at line 1

Solution:

SQL>conn sys as sysdba
SQL>shutdown immediate
SQL>startup upgrade

RUN catalog, catproc and utlrp script from SQL Prompt

SQL>shutdown immediate
SQL>startup
SQL>select comp_name,version,status from dba_registry;

ORA-27492: unable to run job scheduler

My Oracle application have stopped transferring data to another table.
After doing a bit of troubleshooting,I have narrowed the issue down to the scheduled job PERSON.FIG_TIME_DAILY
The procedure that is called by this job works fine when I run in manually
However, this scheduled job hasn't successfully run in over a day
I tried dropping the job entirely and rebuilding it using the DDL from the same job in my testing environment, but that didn't seem to work.

Unable to run job "PERSON.FIG_TIME_DAILY" scheduler unavailable

From the online research I've done, most users have resolved this problem with some variation of the command

SQL>show parameter  job_queue_processes;
the value was default set to 1000

Than i Google out and run the following

SQL>select attribute_name,  value
from dba_scheduler_global_attribute
where attribute_name = 'SCHEDULER_DISABLED';

ATTRIBUTE_NAME     VALUE
------------------ -----
SCHEDULER_DISABLED TRUE

-- Attribute vanishes when set to false (run as sysdba)

SQL>exec dbms_scheduler.set_scheduler_attribute ( 'SCHEDULER_DISABLED', 'FALSE' );

After this Scheduler started Working

ORA - 19625: error identifying file

RMAN> BACKUP DATABASE PLUS ARCHIVELOG DELETE INPUT;

 Starting backup
 current log archived
 using channel ORA_DISK_1
 RMAN-00571: ===========================================================
 RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
 RMAN-00571: ===========================================================
 RMAN-03002: failure of backup plus archivelog command at 10/09/2014 00:16:23
 RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
 ORA-19625: error identifying file /u01/app/oracle/oradata/archive/1_241_850299214.arc
 ORA-27037: unable to obtain file status
 Linux-x86_64 Error: 2: No such file or directory
 Additional information: 3

Cause: RMAN cannot find the following archive log file in corresponding destination cause of expire or delete file.

Solution: You can check your expire archive log list and delete expired archive log files from RMAN, If you really lost your archive log file and you are not able to collect this file.

RMAN> CROSSCHECK ARCHIVELOG ALL;

 released channel: ORA_DISK_1
 allocated channel: ORA_DISK_1
 channel ORA_DISK_1: SID=98 device type=DISK
 validation failed for archived log
 archived log file name=/u01/app/oracle/oradata/archive/1_241_850299214.arc RECID=351 STAMP=860457193
 validation failed for archived log
 archived log file name=/u01/app/oracle/oradata/archive/1_242_850299214.arc RECID=351 STAMP=860457670
 validation succeeded for archived log
 archived log file name=/u01/app/oracle/oradata/archive/1_243_850299214.arc RECID=352 STAMP=860458582
 Crosschecked 3 objects

 RMAN> DELETE EXPIRED ARCHIVELOG ALL;

 released channel: ORA_DISK_1
 allocated channel: ORA_DISK_1
 channel ORA_DISK_1: SID=98 device type=DISK
 List of Archived Log Copies for database with db_unique_name ORA11GS
 =====================================================================

 Key     Thrd Seq     S Low Time
 ------- ---- ------- - ---------
 2730    1    241     X 08-OCT-14
         Name: /u01/app/oracle/oradata/archive/1_241_850299214.arc

 3002    1    242     X 08-OCT-14
         Name: /u01/app/oracle/oradata/archive/1_242_850299214.arc

 Do you really want to delete the above objects (enter YES or NO)? yes
 deleted archived log
 archived log file name=/u01/app/oracle/oradata/archive/1_241_850299214.arc RECID=351 STAMP=860457193
 deleted archived log
 archived log file name=/u01/app/oracle/oradata/archive/1_242_850299214.arc RECID=351 STAMP=860457670
 Deleted 2 EXPIRED objects

 RMAN> BACKUP DATABASE PLUS ARCHIVELOG DELETE INPUT;

 Starting backup
 current log archived
 using channel ORA_DISK_1
 channel ORA_DISK_1: starting archived log backup set
 channel ORA_DISK_1: specifying archived log(s) in backup set
 input archived log thread=1 sequence=243 RECID=352 STAMP=860458582
 input archived log thread=1 sequence=244 RECID=353 STAMP=860459023
 channel ORA_DISK_1: starting piece 1 at 09-OCT-14
 channel ORA_DISK_1: finished piece 1 at 09-OCT-14
 piece handle=/u01/rman_backup/ora11gs_bkp_1gpkj40g tag=TAG20141009T002344 comment=NONE
 channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
 channel ORA_DISK_1: deleting archived log(s)
 archived log file name=/u01/app/oracle/oradata/archive/1_243_850299214.arc RECID=352 STAMP=860458582
 archived log file name=/u01/app/oracle/oradata/archive/1_244_850299214.arc RECID=353 STAMP=860459023
 Finished backup at 09-OCT-14

 Starting backup at 09-OCT-14
 using channel ORA_DISK_1
 channel ORA_DISK_1: starting full datafile backup set
 channel ORA_DISK_1: specifying datafile(s) in backup set
 input datafile file number=00001 name=/u01/app/oracle/oradata/ora11gp/system01.dbf
 input datafile file number=00002 name=/u01/app/oracle/oradata/ora11gp/sysaux01.dbf
 input datafile file number=00003 name=/u01/app/oracle/oradata/ora11gp/undotbs01.dbf
 input datafile file number=00004 name=/u01/app/oracle/oradata/ora11gp/users01.dbf
 channel ORA_DISK_1: starting piece 1
 channel ORA_DISK_1: finished piece 1
 piece handle=/u01/rman_backup/ora11gs_bkp_1hpkj40h tag=TAG20141009T002345 comment=NONE
 channel ORA_DISK_1: backup set complete, elapsed time: 00:01:25
 Finished backup

 Starting backup
 current log archived
 using channel ORA_DISK_1
 channel ORA_DISK_1: starting archived log backup set
 channel ORA_DISK_1: specifying archived log(s) in backup set
 input archived log thread=1 sequence=245 RECID=354 STAMP=860459111
 channel ORA_DISK_1: starting piece 1 at 09-OCT-14
 channel ORA_DISK_1: finished piece 1 at 09-OCT-14
 piece handle=/u01/rman_backup/ora11gs_bkp_1ipkj437 tag=TAG20141009T002511 comment=NONE
 channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
 channel ORA_DISK_1: deleting archived log(s)
 archived log file name=/u01/app/oracle/oradata/archive/1_245_850299214.arc RECID=354 STAMP=860459111
 Finished backup

 Starting Control File and SPFILE Autobackup
 piece handle=/u01/rman_backup/bkp_cf_c-3519562480-20141009-01 comment=NONE
 Finished Control File and SPFILE Autobackup

 RMAN> 

ORA-38706: Cannot turn on FLASHBACK DATABASE logging

SQL> alter database flashback on;
 alter database flashback on
 *
 ERROR at line 1:
 ORA-38706: Cannot turn on FLASHBACK DATABASE logging.
 ORA-38707: Media recovery is not enabled.

Cause : For enable flashback database must be archive mode. To resolve this error enable archive log mode.

SQL>SHUTDOWN IMMEDIATE;

SQL> STARTUP MOUNT;
ORACLE instance started.

Total System Global Area  630501376 bytes
Fixed Size                  2215984 bytes
Variable Size             381685712 bytes
Database Buffers          243269632 bytes
Redo Buffers                3330048 bytes
Database mounted.

SQL> archive log list;

Database log mode              No Archive Mode
Automatic archival             Disabled
Archive destination            /u01/app/oracle/oradata/archive
Oldest online log sequence     434
Current log sequence           436

SQL> alter database archivelog;
Database altered.

SQL> alter database flashback on;
Database altered.

SQL>alter database open;
database altered

SQL>select flashback_on from v$database;
FLASHBACK_ON
--------------------
ON

INS-10002 Inventory Initialization failed

This error occurs when installing Oracle Client_32 bit on Windows 64 bit Server

To resolve this error, delete Registry Entry "inst_loc"

Type Regedit in "Run" Dialog Box from Start Menu

Go to HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE

and Delete "inst_loc"

Close the Registry and install Oracle Client 12c again

Try deleting repository before Creating Repository

This error might occur if there is an existing repository

To solve this error

Delete the Repository

or

Drop Oracle user who has created the Repository and again recreate it

Failure I/O Error: SSO failed:Native SSPI not loaded. Check the java.library.path system property

This Failure is due to connection fail between Oracle SQL Developer to MS SQL Server Database

Copy
JDIST file ntlmauth.dll to Java path in your System

D:\jtds-1.3.1-dist\x64\SSO\ntlmauth.dll

To

C:\java\jdk1.8.0_112\bin

After this Check connecting SQL Developer to SQL Server Database

ORA-01031 Insufficient privilege while creating Oracle user

login as "SYS" user

SQL> create user test identified by test;
ORA-01031: insufficient privilege

If you have "Enabled" Oracle Database Vault in your Database this could cause a problem

Solution is Disable Oracle Database Vault

SQL>exec dbms_macadam.disable_dv;

Restart the Database

SQL>create user test identified by test;
User created

SQL>

ORA-00119: invalid specification for system parameter LOCAL_LISTENER

I’ve recently installed an Oracle 12c Release 2 database on Linux and when I bounce the database (using the Shutdown and Startup commands), the database is unable to start

SQL> startup
ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00132: syntax error or unresolved network name 'LISTENER_LAB11'

This is due to the lack of a LOCAL_LISTENER, that must be defined in the TNSNAMES.ORA, according to the Oracle Database Reference 12cR2:

LOCAL_LISTENER specifies a network name that resolves to an address or address list of Oracle Net local listeners
(that is, listeners that are running on the same machine as this instance)

The address or address list is specified in the TNSNAMES.ORA file or other address repository as configured for your system.

So, in your TNSNAMES.ORA (not in LISTENER.ORA) you must define this entry for the local listener:

LISTENER_LAB11.WORLD =
 (ADDRESS = (PROTOCOL = TCP)(HOST = toralin1)(PORT = 1521))

And now you can startup the database. Be sure to set the .WORLD if you have the parameter NAMES.DEFAULT_DOMAIN set at SQLNET.ORA

You can learn more about the LOCAL_LISTENER in this excellent post of Ed Stevens: Exploring the LOCAL_LISTENER parameter

ORA - 39087 Directory Name is invalid

This error occurs because of Directory permissions in Oracle Data Pump during Export / Import

Resolution

SQL> grant read, write on directory <Directory_Name> to <Schema_Name>;

PLS - 00201 Identifier 'dbms_reputil' must be declared

Solution:

sqlplus / as sysdba

SQL>grant execute on dbms_reputil to public;

SQL>exit