ORA-01994: GRANT failed: password file missing or disabled

July 11, 2017, 4:42 am

≫ Next: ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type.

≪ Previous: Apache/bin/httpd:error while loading shared libraries libdb.so.2

$

0

0

ERROR:

ORA-01994: GRANT failed: password file missing or disabled


SOLUTION:
1)Log in  as the same user who owns the file $ORACLE_HOME
and create the password file as follows.

$orapwd file=$ORACLE_HOME/dbs/orapw$ORACLE_SID password=password entries=5 force=y

2)Now grant sysdba privilege to the users that you need. Check V$PWFILE_USERS for the entry.
SQL>GRANT SYSDBA to SYSTEM;

3)Check the owner of $ORACLE_HOME/dbs/orapw$ORACLE_SID verify the password file,

SQL> !ls -l $ORACLE_HOME/dbs/orapw$ORACLE_SID
-rw-r-----   1 oracle   oinstall    2560 Dec 24  2015 /d01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwPROD1

4)If it is not to dba then change the ownership by
$chown oracle:dba $ORACLE_HOME/dbs/orapw$ORACLE_SID

Also change permission by,
$chmod 4640 $ORACLE_HOME/dbs/orapw$ORACLE_SID

---

ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type.

July 11, 2017, 4:43 am

≫ Next: R12: "Cannot Complete Applications Logon" and "APP-FND-01496" Errors When Starting Forms Using RAC

≪ Previous: ORA-01994: GRANT failed: password file missing or disabled

$

0

0

ERROR:

ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type.

CAUSE:

The parameter UNDO_MANAGEMENT is set to AUTO but the undo_tablespace does not exist or is not of type undo (i.e. the contents column of dba_tablespaces does not show 'undo' for this tablespace).

SOLUTION:

Do the following steps to open the database:

1. set undo_management=MANUAL in your init file.

2. connect "/ as sysdba" and startup the database using this init file (if not it will use the SPFILE by default), e.g.:

SQL> startup pfile=<specify>

3. drop the ('undo') tablespace if you wrongly created one without actually specifying "undo"

4. create a new undo tablespace, e.g.:

SQL> create UNDO tablespace undotbs datafile '/DB1/undotbs01.dbf' size 1M reuse;

5. shutdown the database

6. change UNDO_MANAGEMENT=AUTO in your init file and set UNDO_TABLESPACE=UNDOTBS (or whatever name you specified during the undo tablespace creation)

7. connect "/ as sysdba" and startup the database using this init file (as in step 2).

Now the database will open using the new undo tablespace and it would have created new undo segments in this tablespace.

R12: "Cannot Complete Applications Logon" and "APP-FND-01496" Errors When Starting Forms Using RAC

July 11, 2017, 4:45 am

≫ Next: ORA-00600: internal error code, arguments: [kkocxj : pjpCtx], [], [], [], [], [], [], []

≪ Previous: ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type.

$

0

0

R12: "Cannot Complete Applications Logon" and "APP-FND-01496" Errors When Starting Forms Using RAC

Oracle EBS Applications Version -12.1.3

Symptoms

When using RAC database the following sequence of error dialogs is shown when starting Forms function from the Homepage.

               

The error happens intermittently. Sometimes Forms is started without any problems on the first attempt. When the error is raised trying a second or third time makes Forms is then started as expected.

Running the 'date' command (at the same moment) on all RAC nodes show a different time stamp. The example below shows a 2 minute difference between the 2 RAC nodes:

Node 1:
Thu Jun 29 11:16:14 IST 2017

Node 2:
Thu Jun 29 11:14:01 IST 2017

Changes

Network Maintenance and Missing some firewall settings.

Cause

The root-cause here is the time difference between the RAC nodes

Solution

Synchronize the time on all the RAC Nodes. Follow the following sequence of actions: - Stop all Applications Middle Tier Services - Stop all RAC Clusterware Services - Synchronize the time between all RAC nodes (for example using NTP (*)) - Restart the RAC Clusterware Services - Restart the Applications Middle Tier Services - Test starting Forms from the Homepage .

ORA-00600: internal error code, arguments: [kkocxj : pjpCtx], [], [], [], [], [], [], []

July 11, 2017, 4:46 am

≫ Next: FDUUID failed due to ORA-08004: sequence FND_CONCURRENT_PROCESSES_S.NEXTVAL exceeds MAXVALUE and cannot be instantiated.

≪ Previous: R12: "Cannot Complete Applications Logon" and "APP-FND-01496" Errors When Starting Forms Using RAC

$

0

0

Error:

=====

When we connect the database in the toadwe are getting the error.

ORA-00600: internal error code, arguments: [kkocxj : pjpCtx], [], [], [], [], [], [], []

Symptoms

=========

ORA-00600 [kkocxj : pjpCtx] error is reported when running a complex query.

Cause

======

Bug 7014646: INTERNAL ERROR CODE, ARGUMENTS: [KKOCXJ : PJPCTX], [], [], [], [], []

Call stack includes:

kkocxj <- kkoiqb <- kkooqb <- kkoqbc <- apakkoqb <- apaqbdDescendents <- apaqbdListReverse

   <- apaqbd <- kkqctCostTransfQB <- kkqctdrvJP <- kkqjpdttr <- kkqjpdttr <- kkqctdrvTD <- kkqjpddrv

      <- kkqdrv <- kkqctdrvIT <- apadrv <- opitca <- kksFullTypeCheck <- rpiswu2 <- kksLoadChild

         <- kxsGetRuntimeLock <- kksfbc <- kkspbd0 <- kksParseCursor <- opiosq0 <- opipls <- opiodr

            <- rpidrus <- skgmstack <- rpidru <- rpiswu2 <- rpidrv <- psddr0 <- psdnal

If a PUSH_PRED hint containing a predicate number is present in the culprit query, then this could be Bug 5637915.

Solution

Bug 7014646 is fixed in 10.2.0.5 , 11.1.0.7  and 11.2.0.1

For earlier DB versions, please apply Patch 7014646 where available

OR

use the following workaround:

SQL> conn / as sysdba

SQL> alter system set "_optimizer_push_pred_cost_based"=false;

SQL> exit

FDUUID failed due to ORA-08004: sequence FND_CONCURRENT_PROCESSES_S.NEXTVAL exceeds MAXVALUE and cannot be instantiated.

July 11, 2017, 4:47 am

≫ Next: ORA-13780: SQL statement does not exist. ORA-06512: at "SYS.DBMS_SYS_ERROR"

≪ Previous: ORA-00600: internal error code, arguments: [kkocxj : pjpCtx], [], [], [], [], [], [], []

$

0

0

Issue:

=====

FDUUID failed due to ORA-08004: sequence FND_CONCURRENT_PROCESSES_S.NEXTVAL exceeds MAXVALUE and cannot be instantiated.

TheCall to establish_icm failed

The Internal Concurrent Manager has encountered an error.

Cause:

======

SQL> select FND_CONCURRENT_PROCESSES_S.nextval from dual;

select FND_CONCURRENT_PROCESSES_S.nextval from dual

*

ERROR at line 1:

ORA-08004: sequence FND_CONCURRENT_PROCESSES_S.NEXTVAL exceeds MAXVALUE and

cannot be instantiated

The FND_CONCURRENT_PROCESSES_S Max value is reached. we need to increase this value

SQL> select * from dba_sequences

where sequence_name = ‘FND_CONCURRENT_PROCESSES_S’ 2 ;

SEQUENCE_OWNER SEQUENCE_NAME MIN_VALUE MAX_VALUE INCREMENT_BY C O CACHE_SIZE LAST_NUMBER

—————————— —————————— ———- ———- ———— – – ———- ———–

APPLSYS FND_CONCURRENT_PROCESSES_S 1 9999999 67778 N N 1000 10048596

Solution:

=========

Increase max value;(shoud be greater Than previoue Max value)

SQL> ALTER SEQUENCE APPLSYS.FND_CONCURRENT_PROCESSES_S MAXVALUE 99999999;

Sequence altered.

Doc: Concurrent Manager Does Not Startup ORA-08004: sequence FND_CONCURRENT_PROCESSES_S.NEXTVAL exceeds MAXVALUE

ORA-13780: SQL statement does not exist. ORA-06512: at "SYS.DBMS_SYS_ERROR"

July 11, 2017, 4:47 am

≫ Next: APP-FND-01388

≪ Previous: FDUUID failed due to ORA-08004: sequence FND_CONCURRENT_PROCESSES_S.NEXTVAL exceeds MAXVALUE and cannot be instantiated.

$

0

0

Error:

====

When we run the sql_tuning_task we are getting the below error in the database.

SQL> SET SERVEROUTPUT ON

SQL>

SQL> DECLARE

2 L_SQL_TUNE_TASK_ID VARCHAR2(100);

3 BEGIN

4 L_SQL_TUNE_TASK_ID := DBMS_SQLTUNE.CREATE_TUNING_TASK (

5 SQL_ID => 'fcs0af97qvuft',

6 SCOPE => DBMS_SQLTUNE.SCOPE_COMPREHENSIVE,

7 TIME_LIMIT => 600,

8 TASK_NAME => 'fcs0af97qvuft_task',

9 DESCRIPTION => 'Tuning task for fcs0af97qvuft');

10 DBMS_OUTPUT.PUT_LINE('l_sql_tune_task_id: ' || L_SQL_TUNE_TASK_ID);

11 END;

12 /

DECLARE

*

ERROR AT LINE 1:

ORA-13780: SQL statement does not exist.

ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79

ORA-06512: at "SYS.PRVT_SQLADV_INFRA", line 125

ORA-06512: at "SYS.DBMS_SQLTUNE", line 655

ORA-06512: at line 4

Solution:

========

1. The sql_id is not exist on the server.

2.If I specify in the task 2 snapshots that include an execution of the particular SQL statement, I get no error:

APP-FND-01388

July 11, 2017, 4:48 am

≫ Next: AC-50480: Internal error occurred: java.lang.Exception: Error while generating listener.ora

≪ Previous: ORA-13780: SQL statement does not exist. ORA-06512: at "SYS.DBMS_SYS_ERROR"

$

0

0

APP-FND-01388:

=============

Error:

=====

 Cannot read value for profile option FND_MGR_STRTUP_THRES_TIME in routine &ROUTINE.

Issue: APP-FND-01388: Cannot read value for profile option FND_MGR_STRTUP_THRES_TIME in routine &ROUTINE.

Routine FDPCRQ encountered an ORACLE error. ORA-04031: unable to

allocate 32 bytes of shared memory ("shared pool".

Review your error messages for the cause of the error. (=<POINTER>)

Solution:

=======

If the database parameter named _memory_broker_stat_interval has not been explicitely set to a value of 999 as per solution #3 of note 'Common Cause for ORA-4031 in 10gR2, Excess "KGH: NO ACCESS" Memory Allocation [Video]' (Doc ID 801787.1) then I would start with solution #3to see if that change alone is enough to avoid further ORA-04031 errors (especially if the failed allocation requests are for 32 bytes).

ALTER SYSTEM SET "_memory_broker_stat_interval"=999 SCOPE=SPFILE;

Then the instance would need to be restarted for the change to take effect.

AC-50480: Internal error occurred: java.lang.Exception: Error while generating listener.ora

July 11, 2017, 4:49 am

≫ Next: FRM-92101: There was a failure in form server during startup

≪ Previous: APP-FND-01388

$

0

0

AC-50480: Internal error occurred: java.lang.Exception: Error while generating listener.ora

PROBLEM:

=========

Encounter the following error when running autoconfig on the Application  Tier.

ERROR:

=======

Updating s_tnsmode to ‘generateTNS’

UpdateContext exited with status: 0

AC-50480: Internal error occurred: java.lang.Exception: Error while generating listener.ora.

Error generating tnsnames.ora from the database, temporary tnsnames.ora will be generated using templates

Instantiating Tools tnsnames.ora

Tools tnsnames.ora instantiated

Web tnsnames.ora instantiated

adgentns.pl exiting with status 2

ERRORCODE = 2 ERRORCODE_END

.end std out.

SOLUTION:

==========

There is no information in the table FND_NODES for the database node. Which means that autoconfig has not executed on the Database Tier.

First need to run autoconfig on the database tier to populate the database node values in FND_NODES table then run autoconfig on Application Tier.

please execute the following steps:

1. Loging to as oracle user and perform the below steps

sqlplus apps/$apps

exec fnd_conc_clone.setup_clean

2. Run autoconfig.sh on db node.

3. Run autocnfig.sh on apps node.

Thank You !!

---

FRM-92101: There was a failure in form server during startup

July 11, 2017, 4:49 am

≫ Next: OGG-00446 Supplemental checkpoint table does not exist. Create a supplemental checkpoint table with the UPGRADE CHECKPOINTTABLE command in GGSCI if you have upgraded from release 11.2.1.0.0 or earlier.

≪ Previous: AC-50480: Internal error occurred: java.lang.Exception: Error while generating listener.ora

$

0

0

FRM-92101: There was a failure in form server during startup

After performing R12.1  EBS clone for one of our customer we were not able to access EBS forms due to frm-92101 error. Forms was not launching.

Cause:

=====

One of the application dependent library file is still exists with the old production OS username - oraprod where as system is expecting this link should be owned by oratest user (clone)

RM-92101:There Was A Failure In The Forms Server During Startup.This Could Happen Due To Invalid Configuration When Opening Forms (Doc ID 1931394.1)

This is due to ldflags pointing to wrongly to PROD server which should points to (TEST/DEV) respective server.

[oratest@ORAEBSBKP[/oratest/R12_app/apps/tech_st/10.1.2/lib32]#ls -lrt ldflags lrwxrwxrwx 1 oraprod dba 44 Feb  5 15:42 ldflags -> /oraprod/R12/apps/tech_st/10.1.2/lib/ldflags

Solution:

=======

1) remove soft link for ldflags

2) create new softlink

3) stop application services

4)  run make command for form libraries

5) start application services

Solution:

=======

Source the Apps environment

Bring down the application

Cd $ORACLE_HOME/lib32

ls –lrt ldflags  -Would be pointing to production location

unlink  ldflags

ln -s   /u01/test/apps/tech_st/10.1.2/lib/ldflags ldflags (link to the right path)

cd $ORACLE_HOME/forms/lib32/

make -f ins_forms.mk install

Now restart the application and check for the same.

OGG-00446 Supplemental checkpoint table does not exist. Create a supplemental checkpoint table with the UPGRADE CHECKPOINTTABLE command in GGSCI if you have upgraded from release 11.2.1.0.0 or earlier.

July 12, 2017, 9:42 pm

≫ Next: OGG-00529 Oracle GoldenGate Capture for Oracle, lsrcet.prm: DDL Replication is enabled but table ggs_owner.GGS_DDL_HIST is not found. Please check DDL installation in the database

≪ Previous: FRM-92101: There was a failure in form server during startup

$

0

0

OGG-00446  Supplemental checkpoint table does not exist. Create a supplemental checkpoint table with the UPGRADE CHECKPOINTTABLE command in GGSCI if you have upgraded from release 11.2.1.0.0 or earlier.


GGSCI (dbhost02.domain.com) 3> info all

Program     Status      Group  Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
EXTRACT     RUNNING     EXT     00:00:00      00:00:06
REPLICAT    STOPPED     REP     00:00:00      00:04:15

GGSCI (dbhost02.domain.com) 6>UPGRADE CHECKPOINTTABLE GGUSER_CHECKPOINT

1. When we are execute above command the issue will be resolved.After restart the replicat process the same error will comes means we need to Delete the checkpoint table.

2. After that add the checkpoint table and restart the replicat process the issue will be resolved

GGSCI(dbhost02.domain.com) DELETE CHECKPOINTTABLE GGUSER_CHECKPOINT
GGSCI(dbhost02.domain.com) ADD CHECKPOINTTABLE GGUSER_CHECKPOINT
GGSCI(dbhost02.domain.com) 5> info all

Program     Status      Group  Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
EXTRACT     RUNNING     EXT     00:00:02      00:00:26
REPLICAT    RUNNING     REP     02:35:52      00:00:16

OGG-00529 Oracle GoldenGate Capture for Oracle, lsrcet.prm: DDL Replication is enabled but table ggs_owner.GGS_DDL_HIST is not found. Please check DDL installation in the database

July 13, 2017, 1:57 am

≫ Next: OGG-02550 ORACLE_HOME is not set to Oracle software directory.

≪ Previous: OGG-00446 Supplemental checkpoint table does not exist. Create a supplemental checkpoint table with the UPGRADE CHECKPOINTTABLE command in GGSCI if you have upgraded from release 11.2.1.0.0 or earlier.

$

0

0

OGG-00529  Oracle GoldenGate Capture for Oracle, lsrcet.prm:  DDL Replication is enabled but table ggs_owner.GGS_DDL_HIST is not found. Please check DDL installation in the database

DDL support scripts should be run in source database:

GGSCI (dbhost01.domain.com) 11> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
EXTRACT     RUNNING     DPUMP1      00:00:00      00:00:04
EXTRACT     STOPPED     EXT1        00:00:00      00:31:08

REPLICAT    RUNNING     REP1        00:00:00      00:00:08

SQL> alter system set recyclebin=off scope=spfile;

System altered.

cd $GG_HOME
[oracle@dbhost01 oggcore_1]$ !sq
sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Thu Jul 13 14:15:16 2017

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


Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> @marker_setup.sql

Marker setup script

You will be prompted for the name of a schema for the Oracle GoldenGate database objects.
NOTE: The schema must be created prior to running this script.
NOTE: Stop all DDL replication before starting this installation.

Enter Oracle GoldenGate schema name:gguser


Marker setup table script complete, running verification script...
Please enter the name of a schema for the GoldenGate database objects:
Setting schema name to GGUSER

MARKER TABLE
-------------------------------
OK

MARKER SEQUENCE
-------------------------------
OK

Script complete.
SQL> @ddl_setup.sql

Oracle GoldenGate DDL Replication setup script

Verifying that current user has privileges to install DDL Replication...

You will be prompted for the name of a schema for the Oracle GoldenGate database objects.
NOTE: For an Oracle 10g source, the system recycle bin must be disabled. For Oracle 11g and later, it can be enabled.
NOTE: The schema must be created prior to running this script.
NOTE: Stop all DDL replication before starting this installation.

Enter Oracle GoldenGate schema name:gguser

Working, please wait ...
Spooling to file ddl_setup_spool.txt

Checking for sessions that are holding locks on Oracle Golden Gate metadata tables ...

Check complete.







WARNING: Tablespace GGUSER01 does not have AUTOEXTEND enabled.



Using GGUSER as a Oracle GoldenGate schema name.

Working, please wait ...

DDL replication setup script complete, running verification script...
Please enter the name of a schema for the GoldenGate database objects:
Setting schema name to GGUSER

CLEAR_TRACE STATUS:

Line/pos   Error
---------- -----------------------------------------------------------------
No errors  No errors

CREATE_TRACE STATUS:

Line/pos   Error
---------- -----------------------------------------------------------------
No errors  No errors

TRACE_PUT_LINE STATUS:

Line/pos   Error
---------- -----------------------------------------------------------------
No errors  No errors

INITIAL_SETUP STATUS:

Line/pos   Error
---------- -----------------------------------------------------------------
No errors  No errors

DDLVERSIONSPECIFIC PACKAGE STATUS:

Line/pos   Error
---------- -----------------------------------------------------------------
No errors  No errors

DDLREPLICATION PACKAGE STATUS:

Line/pos   Error
---------- -----------------------------------------------------------------
No errors  No errors

DDLREPLICATION PACKAGE BODY STATUS:

Line/pos   Error
---------- -----------------------------------------------------------------
No errors  No errors

DDL IGNORE TABLE
-----------------------------------
OK

DDL IGNORE LOG TABLE
-----------------------------------
OK

DDLAUX  PACKAGE STATUS:

Line/pos   Error
---------- -----------------------------------------------------------------
No errors  No errors

DDLAUX PACKAGE BODY STATUS:

Line/pos   Error
---------- -----------------------------------------------------------------
No errors  No errors

SYS.DDLCTXINFO  PACKAGE STATUS:

Line/pos   Error
---------- -----------------------------------------------------------------
No errors  No errors

SYS.DDLCTXINFO  PACKAGE BODY STATUS:

Line/pos   Error
---------- -----------------------------------------------------------------
No errors  No errors

DDL HISTORY TABLE
-----------------------------------
OK

DDL HISTORY TABLE(1)
-----------------------------------
OK

DDL DUMP TABLES
-----------------------------------
OK

DDL DUMP COLUMNS
-----------------------------------
OK

DDL DUMP LOG GROUPS
-----------------------------------
OK

DDL DUMP PARTITIONS
-----------------------------------
OK

DDL DUMP PRIMARY KEYS
-----------------------------------
OK

DDL SEQUENCE
-----------------------------------
OK

GGS_TEMP_COLS
-----------------------------------
OK

GGS_TEMP_UK
-----------------------------------
OK

DDL TRIGGER CODE STATUS:

Line/pos   Error
---------- -----------------------------------------------------------------
No errors  No errors

DDL TRIGGER INSTALL STATUS
-----------------------------------
OK

DDL TRIGGER RUNNING STATUS
-----------------------------------
ENABLED

STAYMETADATA IN TRIGGER
-----------------------------------
OFF

DDL TRIGGER SQL TRACING
-----------------------------------
0

DDL TRIGGER TRACE LEVEL
-----------------------------------
NONE

LOCATION OF DDL TRACE FILE
------------------------------------------------------------------------------------------------------------------------
/u02/app/oracle/product/12.1.0/dbhome_1/rdbms/log/ggs_ddl_trace.log

Analyzing installation status...


VERSION OF DDL REPLICATION
------------------------------------------------------------------------------------------------------------------------
OGGCORE_12.2.0.1.0_PLATFORMS_151211.1401

STATUS OF DDL REPLICATION
------------------------------------------------------------------------------------------------------------------------
SUCCESSFUL installation of DDL Replication software components

Script complete.
SQL> @role_setup.sql

GGS Role setup script

This script will drop and recreate the role GGS_GGSUSER_ROLE
To use a different role name, quit this script and then edit the params.sql script to change the gg_role parameter to the preferred name. (Do not run the script.)

You will be prompted for the name of a schema for the GoldenGate database objects.
NOTE: The schema must be created prior to running this script.
NOTE: Stop all DDL replication before starting this installation.

Enter GoldenGate schema name:gguser
Wrote file role_setup_set.txt

PL/SQL procedure successfully completed.


Role setup script complete

Grant this role to each user assigned to the Extract, GGSCI, and Manager processes, by using the following SQL command:

GRANT GGS_GGSUSER_ROLE TO <loggedUser>

where <loggedUser> is the user assigned to the GoldenGate processes.
SQL> GRANT GGS_GGSUSER_ROLE TO gguser;

Grant succeeded.

SQL> @ddl_enable

Trigger altered.

GGSCI (dbhost01.domain.com) 12> start ext1

Sending START request to MANAGER ...
EXTRACT EXT1 starting


GGSCI (dbhost01.domain.com) 13> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
EXTRACT     RUNNING     DPUMP1      00:00:00      00:00:00
EXTRACT     RUNNING     EXT1        00:00:00      00:00:01
REPLICAT    RUNNING     REP1        00:00:00      00:00:05

OGG-02550 ORACLE_HOME is not set to Oracle software directory.

July 13, 2017, 2:11 am

≫ Next: Fs_clone - adop Fails with Status 2

≪ Previous: OGG-00529 Oracle GoldenGate Capture for Oracle, lsrcet.prm: DDL Replication is enabled but table ggs_owner.GGS_DDL_HIST is not found. Please check DDL installation in the database

$

0

0

2016-03-10 15:14:32  ERROR   OGG-02550  ORACLE_HOME is not set to Oracle software directory.

2016-03-10 15:14:32  ERROR   OGG-01668  PROCESS ABENDING.

GGSCI (dbhost02.domain.com) 5> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
EXTRACT     RUNNING     DPUMP1      00:00:00      00:00:04
EXTRACT     STOPPED     EXT1        00:00:00      00:19:06
REPLICAT    RUNNING     REP2        00:00:00      00:00:08

GGSCI (dbhost02.domain.com) 6> view params EXT1

EXTRACT ext1
USERID gguser, PASSWORD ora123
EXTTRAIL /u02/app/oracle/product/12.1.0/oggcore_1/dirdat/aa
TRANLOGOPTIONS EXCLUDEUSER gguser
TABLE app.emp;
DDL INCLUDE MAPPED

Please note that if you have one GoldenGate installation for multiple databases this will not be possible and you will have to set those variables in the extract and replicat processes directly using:

SETENV (ORACLE_HOME = "path to Oracle home location")
SETENV (ORACLE_SID = "SID")


EXTRACT ext1
USERID gguser, PASSWORD ora123
EXTTRAIL /u02/app/oracle/product/12.1.0/oggcore_1/dirdat/aa
TRANLOGOPTIONS EXCLUDEUSER gguser
TABLE app.emp;
SETENV (ORACLE_HOME = "/u02/app/oracle/product/12.1.0/dbhome_1")
SETENV (ORACLE_SID = "ORAGG1")
DDL INCLUDE MAPPED

After adding the variable to restart the extract process.

GGSCI (dbhost02.domain.com) 7> start EXT1

GGSCI (dbhost02.domain.com) 8> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
EXTRACT     RUNNING     DPUMP1      00:00:00      00:00:04
EXTRACT     RUNNING     EXT1        00:00:00      00:19:06
REPLICAT    RUNNING     REP2        00:00:00      00:00:08

Fs_clone - adop Fails with Status 2

July 13, 2017, 2:59 pm

≫ Next: OGG-02022 Logmining server does not exist on this Oracle database.

≪ Previous: OGG-02550 ORACLE_HOME is not set to Oracle software directory.

$

0

0

We have faced issue when we run adop phase=fs_clone.

adop phase=fs_clone
adop exiting with status = 2 (Fail)

When checked logfile noticed following entries.

[UNEXPECTED]fs_clone has failed.
 [PROCEDURE] [START 2017/07/13 13:55:34] Unlocking sessions table
 [STATEMENT] Unlocking ad_adop_sessions table for erpdbtest01 with wait interval of 60 seconds and number of tries 2


Solution:

1. Shut down all the Apps services  from RUN and PATCH file system.

2. Bounce  the database and Run Autoconfig on database.

3. Ensure that no processes are running from PATCH file system.  

4. Run AutoConfig on the RUN file system and start all Apps services on the RUN file system.

5. Re-run FS_CLONE using the following command:

adop phase=fs_clone force=yes

Happy  EBS Troubleshooting  ..

OGG-02022 Logmining server does not exist on this Oracle database.

July 14, 2017, 3:07 am

≫ Next: OGG-00446 No data selecting position from checkpoint table gguser.ckpt for group 'REP1', key 3066872255 (0xb6ccc1bf), SQL .

≪ Previous: Fs_clone - adop Fails with Status 2

$

0

0

Logmining server does not exist on this Oracle database.


2017-02-28 16:27:56  ERROR   OGG-02022  Oracle GoldenGate Capture for Oracle, ext.prm:  Logmining server does not exist on this Oracle database.
2017-02-28 16:27:56  ERROR   OGG-01668  PROCESS ABENDING.

Solution:
set the correct DB env and register goldengate extract

GGSCI (dbhost01.domain.com) 4> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
EXTRACT     STOPPED     EXT1      00:00:00      00:33:03
EXTRACT     STOPPED     DPUMP1      00:00:00      00:56:48

GGSCI (dbhost01.domain.com) 6> dblogin useridalias ggadmin
Successfully logged into database.

GGSCI (dbhost01.domain.com as gguser@ORAGG1) 7> register Extract EXT1 database

2017-02-28 16:37:40  INFO    OGG-02003  Extract EXT successfully registered with database at SCN 324129978306.


GGSCI (dbhost01.domain.com as gguser@ORAGG1) 16> start EXT1

Sending START request to MANAGER ...
EXTRACT EXT starting

GGSCI (dbhost01.domain.com as gguser@ORAGG1) 8> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
EXTRACT     RUNNING     EXT1      00:00:00      00:00:02
EXTRACT     STOPPED     PUMP      00:00:00      00:59:18

OGG-00446 No data selecting position from checkpoint table gguser.ckpt for group 'REP1', key 3066872255 (0xb6ccc1bf), SQL .

July 14, 2017, 3:40 am

≫ Next: Setting SQL prompt in Oracle

≪ Previous: OGG-02022 Logmining server does not exist on this Oracle database.

$

0

0

Cause: It appears replicat is not registered on CHECKPOINTTABLE (is’t true, it’s registered)

Solution: As a workaround we can ALTER the replicat to the same checkpoint location when we do an INFO REP , DETAIL and then START.

GGSCI (dbhost01.domain.com as gguser@ORAGG1) 43> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
EXTRACT     RUNNING     DPUMP1      00:00:00      04:09:41
EXTRACT     RUNNING     EXT1        00:00:00      00:00:02
REPLICAT    STOPPED     REP1        00:00:00      00:17:32


GGSCI (dbhost01.domain.com as gguser@ORAGG1) 27> info

REPLICAT   REP1     Last Started 2017-05-09 13:03   Status STOPPED
Checkpoint Lag       00:00:00 (updated 02:40:11 ago)
Log Read Checkpoint  File ./dirdat/s5000609
                     2017-07-04 10:51:44.035765  RBA 98381832


GGSCI (dbhost01.domain.com as gguser@ORAGG1) 28> alter REP1 extseqno 00609 extrba 98381832

2017-07-04 14:44:39  INFO    OGG-06594  Replicat REP1 has been altered through GGSCI. Even the start up position might be updated, duplicate suppression remains active in next startup. To override duplicate suppression, start REP1 with NOFILTERDUPTRANSACTIONS option.

REPLICAT altered.


GGSCI (dbhost01.domain.com as gguser@ORAGG1) 29> start REP1

Sending START request to MANAGER ...
REPLICAT REP1 starting

GGSCI (dbhost01.domain.com as gguser@ORAGG1) 48> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
EXTRACT     RUNNING     DPUMP1      00:00:00      00:00:04
EXTRACT     RUNNING     EXT1        00:00:00      00:00:09
REPLICAT    RUNNING     REP1        00:00:00      00:00:02

---

Setting SQL prompt in Oracle

July 14, 2017, 5:36 am

≫ Next: ORA-00031: session marked for kill

≪ Previous: OGG-00446 No data selecting position from checkpoint table gguser.ckpt for group 'REP1', key 3066872255 (0xb6ccc1bf), SQL .

$

0

0

The default prompt in SQL*Plus is SQL>, does not provide any information like who the user is and what the user is connected as. Prior to Oracle9i, we have to do elaborate coding to get the information as the SQL prompt, from Oracle 9.2.0 we can use SET SQLPROMPT along with SQL*Plus predefined variables.

Whenever SQL*PLUS starts up, it looks for a file named glogin.sql under the directory $ORACLE_HOME/sqlplus/admin. If the file is found, it is read and the containing statements executed. This allows to store settings across SQL*PLUS sessions. From Oracle 10g, after reading glogin.sql, SQL*PLUS also looks for a file named login.sql, in the directory from where SQL*PLUS was and in the directory that the environment variable SQLPATH points to, and reads it and executes it. Settings from the login.sql take precedence over settings from glogin.sql.

In Oracle9i, whenever a user connects through SQL*PLUS, Oracle will execute only glogin.sql, from 10g Oracle will execute login.sql as well. From Oracle 10g, the login.sql file is not only executed at SQL*Plus startup time, but also at connect time as well. So SQL prompt will be changed after connect command.

To set SQL prompt permanently, update $ORACLE_HOME/sqlplus/admin/glogin.sql or login.sql

SQLP[ROMPT] {SQL>|text}

TEXT can be predefined substitution variables which are prefixed with an underscore.

_connect_identifier	will display connection identifier.
_date	will display date.
_editor	will display editor name used by the EDIT command.
_o_version	will display Oracle version.
_o_release	will display Oracle release.
_privilege	will display privilege such as SYSDBA, SYSOPER, SYSASM
_sqlplus_release	will display SQL*PLUS release.
_user	will display current user name.

                                                                                                                                      

 The variable _CONNECT_IDENTIFIER was introduced in SQL*Plus 9.2 and _DATE, _PRIVILEGE and _USER were introduced in SQL*Plus 10.1.

_USER
The variable _USER contains the current user name given by SHOW USER. If SQL*Plus is not connected, the variable is defined as an empty string.

SQL> set sqlprompt "_user>"

The SQL*Plus prompt will shows
SYSTEM>
MAHE>

_PRIVILEGE
When SQL*Plus is connected as a privileged user the variable _PRIVILEGE contains the connection privilege "AS SYSBDA" or "AS SYSOPER" or "AS SYSASM". If SQL*Plus is connected as a normal user the variable is defined as an empty string.
SQL> set sqlprompt "_user _privilege>"

The SQL*Plus prompt will shows
SYS AS SYSDBA>
MAHE AS SYSOPER>
ASMADM AS SYSASM>

_CONNECT_IDENTIFIER
The variable _CONNECT_IDENTIFIER contains the connection identifier used to start SQL*Plus. For example, if the SQL*Plus connection string is "hr/my_password@MYSID" then the variable contains MYSID. If you use a complete Oracle Net connection string like "hr/my_password@(DESCRIPTION=(ADDRESS_LIST=...(SERVICE_NAME=MYSID.MYDOMAIN)))" then _CONNECT_IDENTIFIER will be set to MYSID. If the connect identifier is not explicitly specified then _CONNECT_IDENTIFIER contains the default connect identifier Oracle uses for connection. For example, on UNIX it will contain the value in the environment variable ORACLE_SID or TWO_TASK. If SQL*Plus is not connected then the variable is defined as an empty string.

SQL> set sqlprompt "&_user@&_connect_identifier>"
or
SQL> set sqlprompt "_user'@'_connect_identifier>"
The SQL*Plus prompt will shows
SYS@PROD>
SYSTEM@DWH>

_DATE
The variable _DATE can be either dynamic, showing the current date or it can be set to a fixed string. The date is formatted using the value of NLS_DATE_FORMAT and will show time information. By default a DEFINE or dereference using &_DATE will give the date at the time of use. _DATE can be UNDEFINED, or set to a fixed string with an explicit DEFINE command. Dynamic date behavior is re-enabled by defining _DATE to an empty string.If we want to display current date:
SQL> set sqlprompt "_user _privilege 'on' _date>"
SYS AS SYSDBA on 9-AUG-10>

If we want to display the current date & time:
MAHE on 9-AUG-10 at DEVDB> alter session set nls_date_format = 'mm/dd/yyyy hh24:mi:ss';
MAHE on 08/09/2010 13:03:51 at DEVDB>

_EDITOR
The variable _EDITOR contains the external text editor executable name.
set sqlprompt _editor>

The SQL*Plus prompt will shows
vi>

_O_VERSION
The variable _O_VERSION contains a text string showing the database version and available options.
set sqlprompt _o_version>

The SQL*Plus prompt will shows
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production With the Partitioning, Data Mining and Real Application Testing options>

_O_RELEASE
The variable _O_RELEASE contains a string representation of the Oracle database version number. If Oracle database version is 11.1.0.7.0 then the variable contains "1101000700". The Oracle version may be different from the SQL*Plus version if you use Oracle Net to connect to a remote database.

set sqlprompt _o_release>

The SQL*Plus prompt will shows (for 10.2.0.4.0)
1002000400>

_SQLPLUS_RELEASE
The variable _SQLPLUS_RELEASE contains the SQL*Plus version number in a similar format to _O_RELEASE.

set sqlprompt _sqlplus_release>

The SQL*Plus prompt will shows (for 10.2.0.4.0)
1002000400>

SQL> set sqlprompt "_user'@'_connect_identifier:SQL> "
SCOTT@DEVDB:SQL> connect system/manager
SYSTEM@DEVDB:SQL> disconnect
@:SQL> connect OEM/OEM@oemdb
OEM@OEMDB:SQL>

To reset to the default SQL prompt,
SQL> set sqlprompt 'SQL>'

ORA-00031: session marked for kill

July 14, 2017, 12:54 pm

≫ Next: RMAN Backup Based Duplicate Fails with RMAN-20207

≪ Previous: Setting SQL prompt in Oracle

$

0

0

We faced a issue on our test database that one of user requested to kill his sesssion when try "alter system kill session"

ERROR at line 1:

ORA-00031: session marked for kill

The session trying to issue the kill will hang for 60 seconds and then return this “session marked for kill” message. And the target session does not get killed at all.

We can check if the session is doing any rollback at the time using the query below:

SQL> SELECT a.sid, a.username, b.xidusn, b.used_urec, b.used_ublk
 FROM v$session a, v$transaction b
 WHERE a.saddr = b.ses_addr and a.sid=&sid;             -->>> Enter the blocking session SID here (&sid:).

In that situation we need to find the process and kill OS process.

select spid
from v$process a , v$session b
where a.addr=b.paddr and b.sid=&sid;

> Enter the  SID here (&sid:).

OS Kill Command:

on windows

---------------

D:> orakill ORACLE_SID spid

On Unix

------------

 

$ kill -9 spid

For more information refer MOS DOC Id: Kill A Process - Not able to clear session (Doc ID 1493261.1)

Thanks for reading ..

RMAN Backup Based Duplicate Fails with RMAN-20207

July 14, 2017, 3:17 pm

≫ Next: ORA-12528: TNS:listener: all appropriate instances are blocking new connections

≪ Previous: ORA-00031: session marked for kill

$

0

0

While Cloning the database through RMAN Duplicate, faced the below error

 RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of Duplicate Db command at 00/00/000 00:00:00
  RMAN-05501: aborting duplication of target database
  RMAN-06004: ORACLE error from recovery catalog database: RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time
 
CAUSE

 The RMAN duplicate is executed with a target database connection.
 A connection to target database is not allowed when using the "incarnation" keyword as stated in the Database Backup and Recovery Reference:

Duplication with a connection to a target does not support previous database incarnations.
However, you can specify previous incarnations if you are duplicating without a connection to a target database.
 
 
SOLUTION

Set the Database Incarnation back to an incarnation before the last RESETLOG time.


Example commands :

$ rman catalog rman/rman@rclone

RMAN> list incarnation;
      set dbid <dbid before the resetlog time>
      connect target un/pw@<alias>
      reset database to incarnation 2;

ORA-12528: TNS:listener: all appropriate instances are blocking new connections

July 14, 2017, 3:39 pm

≫ Next: RMAN-20079: full resync from primary database is not done

≪ Previous: RMAN Backup Based Duplicate Fails with RMAN-20207

$

0

0

 SQL> connect sys@dc2soc03 as sysdba
Enter password:
ERROR: ORA-12528: TNS:listener: all appropriate instances are blocking new connection

CAUSE:

You might get this error if you encounter with Connections via the listener to an instance that is in RESTRICTED status or in NO MOUNT status.  
The lsnrctl services output will show that the service handler for this instance is in state: BLOCKED or RESTRICTED.


LSNRCTL> status

Services Summary…
Service “PLSExtProc” has 1 instance(s).
  Instance “PLSExtProc”, status UNKNOWN, has 1 handler(s) for this service…
Service “dc2soc03.rnhub.com” has 1 instance(s).
  Instance “dc2soc03”, status BLOCKED, has 1 handler(s) for this service…
Service “dc2soc03_XPT.rnhub.com” has 1 instance(s).
  Instance “dc2soc03”, status BLOCKED, has 1 handler(s) for this service…
Service “ecentric_XPT.rnhub.com” has 1 instance(s).
  Instance “ecentric”, status READY, has 1 handler(s) for this service…
The command completed successfully


SOLUTION:

Add  (UR = A) in the TNSnames.ora
The (UR=A) clause for TNS connect strings has been created as an enhancement request.

example:

DC2SOC03 =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = xxx.xxx.xx.xx)(PORT = 1521))
    )
    (CONNECT_DATA =
      (SERVICE_NAME = DC2SOC03.rnhub.com)
            (UR = A)
    )
  )

RMAN-20079: full resync from primary database is not done

July 14, 2017, 5:37 pm

≫ Next: ORA-09925: Unable to create audit trail file WHILE sqlplus / as sysdba

≪ Previous: ORA-12528: TNS:listener: all appropriate instances are blocking new connections

$

0

0

Problem:

RMAN> crosscheck archivelog all;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of crosscheck command at 07/23/2012 09:52:53
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of partial resync command on default channel at 07/23/2012 09:52:53
RMAN-20079: full resync from primary database is not done

Cause:

There are duplicate records in tf table or df table has missing records.


Solution:

1)

Connect catalog DB

SQL> truncate table <catalog_user>.tf;

Crosscheck again.

If it does not work:

2)
Export records of df table that resides in primary database’s catalog schema and import them into standby database’s catalog schema.

Crosscheck again.