Quantcast
Channel: Doyensys Allappsdba Blog..
Viewing all 1640 articles
Browse latest View live

To Resolve ORA-01012: Not Logged On While Starting database

$
0
0
Problem Description
Users cant able to login to database server. Though it allow sys dba to login, it does not allow to run any query. Sometimes it will show database is connected to an idle instance. But when we startup database it shall throw error ORA-01081: cannot start already-running ORACLE - shut it down first.

 $ sqlplus '/as sysdba'

SQL*Plus: Release 11.2.0.3.0 Production on Sat Oct 12 07:53:11 2013

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

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application SAMPLEing options

SQL> select instance_name,status from v$instance;
ERROR at line 1:
ORA-01012: not logged on
SQL> desc v$instance
ERROR:
ORA-01012: not logged on

SQL> startup
ORA-01012: not logged on


Changes
Oracle has been forcefully shutdown at OS level or crashed.

 CAUSE
An orphaned shared memory segment belonging to the ORACLE_SID still exists from a previous instance startup.

The command
ps -ef | grep $ORACLE_SID

shows no processes but with ORACLE_SID set the Oracle 'sysresv' utility shows a shared memory segment for a non-existing instance, e.g.

 $ sysresv

IPC Resources for ORACLE_SID "SAMPLE" :

Shared Memory:
ID              KEY
5963794         0x00000000
5996563         0x00000000
6029332         0xb2e3c9ac

Semaphores:
ID              KEY
No semaphore resources used
Oracle Instance not alive for sid "SAMPLE"


Solution
On OS level, remove the orphaned shared memory segment using:

ipcrm -m <problem shared memory id>

$ ipcrm -m 5963794
$ ipcrm -m 5996563
$ ipcrm -m 6029332

$sqlplus '/as sysdba'

Connected to an idle instance.

SQL> startup Oracle instance started
Total System Global Area   10689474560 bytes
Fixed Size                     2237776 bytes
Variable Size               6375344816 bytes
Database Buffers            4294967296 bytes
Redo Buffers                  16924672 bytes
Oracle Instance Started.
Oracle Database Opened.


Getting ORA-19809: limit exceeded for recovery files

$
0
0
SQL> select * from tab;
select * from tab
              *
ERROR at line 1:
ORA-01219: database not open: queries allowed on fixed tables/views only
 Shutdown the database first
 
 
SQL> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.


Start the database

SQL> startup
ORACLE instance started.

Total System Global Area  599785472 bytes
Fixed Size                  1250356 bytes
Variable Size             180358092 bytes
Database Buffers          411041792 bytes
Redo Buffers                7135232 bytes
Database mounted.
ORA-16038: log 2 sequence# 135 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 2 thread 1:
'F:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG'

Problem: The value db_recovery_file_dest_size is not enough for generate archive log


SQL> show parameter DB_RECOVERY_FILE_DEST_SIZE;

NAME                                 TYPE        VALUE
------------------------------------ ----------- -------------------
db_recovery_file_dest_size           big integer 2G



Solution: Increase the value of db_recovery_file_dest_size following way.

SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 10G;

System altered.


Now open the database.

SQL> alter database open;

Database altered.

Procedure to rebuild datapump metadata? (if corrupted)

$
0
0

Some times, due to some internal errors, datapump utility binaries may get corrupted. In such cases, we can rebuild that using below ways


Oracle database 10.1 version :

SQL> connect / as sysdba

SQL >@ $ORACLE_HOME/rdbms/admin/catdp.sql – this will install metadata

SQL >@ $ORACLE_HOME/rdbms/admin/dbmspump.sql – this will create DBMS procedures for datapump

Oracle database 10.2 version :

SQL >@ $ORACLE_HOME/rdbms/admin/catdph.sql

SQL >@ $ORACLE_HOME/rdbms/admin/prvtdtde.plb

SQL >@ $ORACLE_HOME/rdbms/admin/catdpb.sql

SQL >@ $ORACLE_HOME/rdbms/admin/dbmspump.sql

After performing above steps, all the binaries will be re-build. So, it is better to execute utlrp.sql to recompile invalid objects

SQL >@ $ORACLE_HOME/rdbms/admin/utlrp.sql

Oracle 11g :

SQL >@ $ORACLE_HOME/rdbms/admin/catproc.sql (catproc.sql will take care of all other script execution)

To recompile invalid objects, if any

SQL >@ $ORACLE_HOME/rdbms/admin/utlrp.sql

Note: If you encounter this datapump binaries corruption issue on a production database, before executing above steps,
it is strongly recommended to first test this and based on results you can implement in production

Roll Forward Physical Standby Database using RMAN incremental backup

$
0
0
There would be scenarios where the standby database lags far behind from the primary database leading to Archive Gap. It could be due to one of the following reasons

1. Might be due to the network outage between the primary and the standby database leading to the archive gaps. Data guard would be able to detect the archive gaps automatically and can fetch the missing logs as soon as the connection is re-established.

2. It could also be due to archive logs getting missed out on the primary database or the archives getting corrupted and there would be no valid backups.

In such cases where the standby lags far behind from the primary database, incremental backups can be used as one of the  methods to roll forward the physical standby database to have it in sync with the primary database.

Oracle Database version : 11.2.0.1.0 My Oracle Database is using ASM.

Primary database : sspm              Standby database : sssb

Primary Host : dev                          Standby Host : uat

The maximum archivelog sequence generated on the Primary Database is 1005.

1
2
3
4
5
6
7
8
9
10
11
SQL> select status,instance_name,database_role from v$database,v$instance;

STATUS       INSTANCE_NAME    DATABASE_ROLE
------------ ---------------- ----------------
OPEN         sspm             PRIMARY

SQL> select thread#,max(sequence#) from v$archived_log group bythread#;

THREAD# MAX(SEQUENCE#)
------- ----------------
1       1005
On the standby database, the maximum archivelog sequence that is applied is sequence 865.

1
2
3
4
5
6
7
8
9
10
11
SQL> select status,instance_name,database_role from v$database,v$instance;

STATUS       INSTANCE_NAME    DATABASE_ROLE
------------ ---------------- ----------------
MOUNTED      sssb             PHYSICAL STANDBY

SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;

THREAD# MAX(SEQUENCE#)
------- ----------------
1       865
The standby database is lagging behind the primary database by around 140 archives (1005 – 865).

When I investigated the alert log file of the Primary database  to find out the reason for the logs not getting applied on the standby database, I got to see the below error message.

1
2
3
4
5
Sun Mar 25 15:40:23 2012
Errors in file /u01/app/oracle/diag/rdbms/sspm/sspm/trace/sspm_arc2_18816.trc:
ORA-00308: cannot open archived log '+FRA/sspm/archivelog/2012_03_25/thread_1_seq_866.1117.778865785'
ORA-17503: ksfdopn:2 Failed to open file +FRA/sspm/archivelog/2012_03_25/thread_1_seq_866.1117.778865785
ORA-15012: ASM file '+FRA/sspm/archivelog/2012_03_25/thread_1_seq_866.1117.778865785' does not exist
So the problem was here. The archivelog sequence 866 was missing and was unavailable at the FRA site. There were few more archives missing on the FRA and nor did I had the backup to restore them on the standby database. My option was to go with Roll Forwarding the Standby Database using Incremental Backups. Below are the steps on how to roll forward the physical standby database.

Step 1: Take a note of the Current SCN of the Physical Standby Database.

Standby Database:

1
2
3
4
5
SQL> select current_scn from v$database;

CURRENT_SCN
-----------
991247
Note down the CURRENT_SCN value of the standby database (991247) to proceed further.

Step 2 : Cancel the Managed Recovery Process on the Standby database.

Standby Database:

1
SQL>alter database recover managed standby database cancel;
Step 3: On the Primary database, take the incremental SCN backup from the SCN that is currently recorded on the standby database (991247)

Connect to the primary database and take the incremental SCN backup.

Primary Database:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
[oracle@dev ~]$ rman target sys/oracle@sspm

Recovery Manager: Release 11.2.0.1.0 - Production on Sun Mar 2515:44:45 2012

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

connected to target database: SSPM (DBID=1624493265)

RMAN> backup incremental from scn 991247 database format '/u02/bkp/stnd_backp_%U.bak';

Starting backup at 25-MAR-12

using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=39 device type=DISK
backup will be obsolete on date 01-APR-12
archived logs will not be kept or backed up
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=+DATA_NEW/sspm/datafile/system.256.778803539
input datafile file number=00002 name=+DATA_NEW/sspm/datafile/sysaux.257.778803541
input datafile file number=00003 name=+DATA_NEW/sspm/datafile/undotbs1.258.778803541
input datafile file number=00004 name=+DATA_NEW/sspm/datafile/users.259.778803543
channel ORA_DISK_1: starting piece 1 at 25-MAR-12
channel ORA_DISK_1: finished piece 1 at 25-MAR-12
piece handle=/u02/bkp/stnd_backp_10n6p3nl_1_1.bak tag=TAG20120325T154639 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45

using channel ORA_DISK_1
backup will be obsolete on date 01-APR-12
archived logs will not be kept or backed up
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 25-MAR-12
channel ORA_DISK_1: finished piece 1 at 25-MAR-12
piece handle=/u02/bkp/stnd_backp_11n6p3p4_1_1.bak tag=TAG20120325T154639 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 25-MAR-12
Step 4: Take the standby controlfile backup of the Primary database controlfile.

Connect to the Primary database and create the standby controlfile backup.

Primary Database :

1
2
3
4
5
6
7
8
9
10
11
12
RMAN> backup current controlfile for standby format '/u02/stnd_%U.ctl';

Starting backup at 25-MAR-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including standby control file in backup set
channel ORA_DISK_1: starting piece 1 at 25-MAR-12
channel ORA_DISK_1: finished piece 1 at 25-MAR-12
piece handle=/u02/stnd_12n6p3qt_1_1.ctl tag=TAG20120325T154845 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 25-MAR-12
Step 5: Transfer the backups from the Primary Server to the Standby Server.

Primary Database :

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
[oracle@dev bkp]$ pwd
/u02/bkp
[oracle@dev bkp]$ ls -lrt
total 13576
-rw-r----- 1 oracle oinstall   540672 Mar 25 15:47 stnd_backp_10n6p3nl_1_1.bak
-rw-r----- 1 oracle oinstall 13336576 Mar 25 15:47 stnd_backp_11n6p3p4_1_1.bak
[oracle@dev bkp]$ scp stnd* uat:/u02/bkp
oracle@uat's password:
stnd_backp_10n6p3nl_1_1.bak                   100%  528KB 528.0KB/s   00:00
stnd_backp_11n6p3p4_1_1.bak                   100%   13MB   6.4MB/s   00:02
[oracle@dev bkp]$ cd /u02
[oracle@dev u02]$ ls -lrt stnd*
-rw-r----- 1 oracle oinstall 13336576 Mar 25 15:48 stnd_12n6p3qt_1_1.ctl
[oracle@dev u02]$ scp stnd* uat:/u02
oracle@uat's password:
stnd_12n6p3qt_1_1.ctl                         100%   13MB  12.7MB/s   00:01
[oracle@dev u02]$
Step 6: On the standby server, connect the Standby Database through RMAN and catalog the copied incremental backups so that the Controlfile of the Standby Database would be aware of these incremental backups.

I had the incremental backuppieces copied to the location ‘/u02/bkp‘ on the standby server.

Standby Database:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
[oracle@uat ~]$ rman target sys/mydbpwd@sssb

Recovery Manager: Release 11.2.0.1.0 - Production on Sun Mar 2515:51:02 2012

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

connected to target database: SSPM (DBID=1624493265, not open)

RMAN> catalog start with '/u02/bkp';
Starting implicit crosscheck backup at 25-MAR-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=37 device type=DISK
Crosschecked 15 objects
Finished implicit crosscheck backup at 25-MAR-12

Starting implicit crosscheck copy at 25-MAR-12
using channel ORA_DISK_1
Crosschecked 2 objects
Finished implicit crosscheck copy at 25-MAR-12

searching for all files in the recovery area
cataloging files...
File Name: +arch/SSSB/ARCHIVELOG/2012_03_25/thread_1_seq_200.453.778846881
File Name: +arch/SSSB/ARCHIVELOG/2012_03_25/thread_1_seq_201.454.778846881
File Name: +arch/SSSB/ARCHIVELOG/2012_03_25/thread_1_seq_202.455.778846881
File Name: +arch/SSSB/ARCHIVELOG/2012_03_25/thread_1_seq_203.456.778846881
File Name: +arch/SSSB/ARCHIVELOG/2012_03_25/thread_1_seq_137.457.778846881
File Name: +arch/SSSB/ARCHIVELOG/2012_03_25/thread_1_seq_204.458.778846881
File Name: +arch/SSSB/ARCHIVELOG/2012_03_25/thread_1_seq_205.459.778846883
.
.
.
.

File Name: +arch/SSSB/ARCHIVELOG/2012_03_25/thread_1_seq_856.947.778861691
File Name: +arch/SSSB/ARCHIVELOG/2012_03_25/thread_1_seq_858.949.778861709
File Name: +arch/SSSB/ARCHIVELOG/2012_03_25/thread_1_seq_857.950.778861719

searching for all files that match the pattern /u02/bkp

List of Files Unknown to the Database
=====================================
File Name: /u02/bkp/stnd_backp_10n6p3nl_1_1.bak
File Name: /u02/bkp/stnd_backp_11n6p3p4_1_1.bak

Do you really want to catalog the above files (enter YES or NO)? YES
cataloging files...
cataloging done

List of Cataloged Files
=======================
File Name: /u02/bkp/stnd_backp_10n6p3nl_1_1.bak
File Name: /u02/bkp/stnd_backp_11n6p3p4_1_1.bak
Step 7: Recover the standby database with the cataloged incremental backup pieces.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
RMAN> recover database noredo;

Starting recover at 25-MAR-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=32 device type=DISK
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: +DATA/sssb/datafile/system.274.778865099
destination for restore of datafile 00002: +DATA/sssb/datafile/sysaux.275.778865193
destination for restore of datafile 00003: +DATA/sssb/datafile/undotbs1.276.778865259
destination for restore of datafile 00004: +DATA/sssb/datafile/users.277.778865273
channel ORA_DISK_1: reading from backup piece /u02/bkp/stnd_backp_10n6p3nl_1_1.bak
channel ORA_DISK_1: piece handle=/u02/bkp/stnd_backp_10n6p3nl_1_1.bak tag=TAG20120325T154639
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01

Finished recover at 25-MAR-12
Step 8 : Shutdown the physical standby database, start it in nomount stage and restore the standby controlfile backup that we had taken from the primary database.

Standby Database:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
RMAN> shutdown immediate

database dismounted
Oracle instance shut down

RMAN> startup nomount

connected to target database (not started)
Oracle instance started

Total System Global Area     659730432 bytes

Fixed Size                     2216264 bytes
Variable Size                398462648 bytes
Database Buffers             255852544 bytes
Redo Buffers                   3198976 bytes

RMAN> restore standby controlfile from '/u02/stnd_12n6p3qt_1_1.ctl';

Starting restore at 25-MAR-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=21 device type=DISK

channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:04
output file name=+DATA/sssb/controlfile/current.273.778864875
Finished restore at 25-MAR-12
Step 9: Shutdown the standby database and mount the standby database, so that the standby database would be mounted with the new controlfile that was restored in the previous step.

Standby Database:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
RMAN> <strong>shutdown immediate

Oracle instance shut down

RMAN> startup mount

connected to target database (not started)
Oracle instance started
database mounted

Total System Global Area     659730432 bytes

Fixed Size                     2216264 bytes
Variable Size                398462648 bytes
Database Buffers             255852544 bytes
Redo Buffers                   3198976 bytes
Step 10: If the datafile location of the primary and standby databases are different, then you need to follow this step. If not, then proceed with Step 11.

The datafiles of my primary database are residing on the Diskgroup +DATA_NEW on the primary server and the datafiles on the standby database are residing on the Diskgroup +DATA on the standby server, the datafiles location are different.

Since, I have restored the standby controlfile backuppiece of my primary database on the standby database (Step 7) and mounted the standby database, the standby database controlfile would now have the locations of the datafiles recorded as available in the Primary database. So, we need to make the standby controlfile understand that the datafiles location of the standby database are different from that of the Primary database. For this, you need to catalog the datafile location of the standby database to its controlfile as shown below.

Connect the standby database through RMAN and catalog the location of its datafiles and later switch them.

Standby Database:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
RMAN> catalog start with '+DATA/SSSB/DATAFILE';

searching for all files that match the pattern +DATA/SSSB/DATAFILE

List of Files Unknown to the Database
=====================================
File Name: +data/SSSB/DATAFILE/SYSTEM.274.778865099
File Name: +data/SSSB/DATAFILE/SYSAUX.275.778865193
File Name: +data/SSSB/DATAFILE/UNDOTBS1.276.778865259
File Name: +data/SSSB/DATAFILE/USERS.277.778865273

Do you really want to catalog the above files (enter YES or NO)? YES
cataloging files...
cataloging done

List of Cataloged Files
=======================
File Name: +data/SSSB/DATAFILE/SYSTEM.274.778865099
File Name: +data/SSSB/DATAFILE/SYSAUX.275.778865193
File Name: +data/SSSB/DATAFILE/UNDOTBS1.276.778865259
File Name: +data/SSSB/DATAFILE/USERS.277.778865273

RMAN> switch database to copy;

datafile 1 switched to datafile copy "+DATA/sssb/datafile/system.274.778865099"
datafile 2 switched to datafile copy "+DATA/sssb/datafile/sysaux.275.778865193"
datafile 3 switched to datafile copy "+DATA/sssb/datafile/undotbs1.276.778865259"
datafile 4 switched to datafile copy "+DATA/sssb/datafile/users.277.778865273"

RMAN>
Step 11: If the datafile locations of the primary and the standby databases are same, then there is no necessity to perform the catalogging operation as done in the previous step.

On the standby database, start the Managed Recovery Process.

Standby Database:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
SQL> alter database recover managed standby database disconnectfrom session;

Database altered.

SQL> select process,status,sequence# from v$managed_standby;

PROCESS   STATUS        SEQUENCE#
--------- ------------ ----------
ARCH      CONNECTED             0
ARCH      CONNECTED             0
ARCH      CONNECTED             0
ARCH      CONNECTED             0
RFS       IDLE                  0
RFS       IDLE                  0
RFS       IDLE               1010
RFS       IDLE                  0
MRP0      WAIT_FOR_LOG          0

9 rows selected.
Step 12: On the Primary database, check the Maximum Archivelog Sequence generated.

Primary Database:

1
2
3
4
5
SQL> select thread#,max(sequence#) from v$archived_log group bythread#;

THREAD# MAX(SEQUENCE#)
------- ----------------
1       1009
Step 13: Check the maximum archivelog sequence that is applied on the Physical standby database.

1
2
3
4
5
SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;

THREAD# MAX(SEQUENCE#)
------- ----------------
1       1009
So, here we can see from Steps 12 and 13 that the maximum archivelog sequence generated on the Primary database is sequence# 1009 and that applied on the Physical Standby Database is also 1009 which means that the Standby database is in sync with the Primary Database. You can check it out by generating an archive sequence on the Primary database and check if its shipped and applied on the standby database.

Primary Database:

1
2
3
4
5
6
7
8
9
SQL> alter system switch logfile;

System altered.

SQL> select thread#,max(sequence#) from v$archived_log group bythread#;

THREAD# MAX(SEQUENCE#)
------- ----------------
1       1010
Standby Database:

1
2
3
4
5
SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;

THREAD# MAX(SEQUENCE#)
------- ----------------
1       1010
Now standby database is in sync with the Primary Database.

Here you go !!

Facing ORA-19566 with Free Extents While running RMAN Backup

$
0
0
This is a very interesting case – you got a block corruption on a free block, not associated with any objects extents.  You have no way to recover this block as RMAN will not mind free extents.  I hit this corruption while was doing an RMAN copy.  My file copy failed with,

RMAN> backup INCREMENTAL LEVEL 0 as copy datafile ‘/oradata/bmk/bmk/users01.dbf’  format ‘/oradata/bmk/dbcopy/users01.dbf’;

Starting backup at 14-DEC-10
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=33 device type=DISK
channel ORA_DISK_1: starting datafile copy
input datafile file number=00004 name=/oradata/bmk/bmk/users01.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 12/14/2010 14:35:19
ORA-19566: exceeded limit of 0 corrupt blocks for file /oradata/bmk/bmk/users01.dbf

The alert file shows there is a block corrupt block  – block number 1867 in file 4. 

Tue Dec 14 14:35:12 2010
Hex dump of (file 4, block 1867) in trace file /oradata/oracle/product/10204/diag/rdbms/bmk/bmk/trace/bmk_ora_538.trc
Corrupt block relative dba: 0x0100074b (file 4, block 1867)
Completely zero block found during backing up datafile
Reread of blocknum=1867, file=/oradata/bmk/bmk/users01.dbf. found same corrupt data
Reread of blocknum=1867, file=/oradata/bmk/bmk/users01.dbf. found same corrupt data
Reread of blocknum=1867, file=/oradata/bmk/bmk/users01.dbf. found same corrupt data
Reread of blocknum=1867, file=/oradata/bmk/bmk/users01.dbf. found same corrupt data
Reread of blocknum=1867, file=/oradata/bmk/bmk/users01.dbf. found same corrupt data

Iwent and checked the DBA_EXTENTS, but there were no extents with the block 1867.

SQL>  select SEGMENT_NAME,SEGMENT_TYPE from dba_extents
where FILE_ID=4 and BLOCK_ID <=1867
and block_id+blocks >= 1867;

no rows selected
SQL> select tablespace_name ,bytes/1024/1024
from dba_data_files where file_id=4;

TABLESPACE_NAME                BYTES/1024/1024
—————————— —————
USERS                                    21.25

More over I could track down the block in a free extent.

SQL> select TABLESpace_name from dba_free_space where FILE_ID=4 and BLOCK_ID <=1867
and block_id+blocks >= 1867;

TABLESPACE_NAME
——————————
USERS

I know if I use this block for some objects, Oracle will re-format while re-using.   So, I tried my luck.  I created a new table on the USERS tablespace, as

SQL>  create table test tablespace users  as select * from dba_objects;
Table created.
SQL> select SEGMENT_NAME,SEGMENT_TYPE from dba_extents where FILE_ID=4 and BLOCK_ID <=1867 and block_id+blocks >= 1867;

no rows selected

 No luck,  as Oracle did not use the problem block in the free extent.  Then I moved my TEST table till Oracle used the problem block.

SQL> alter table test move ;

Table altered.

SQL> select TABLESpace_name from dba_free_space where FILE_ID=4 and BLOCK_ID <=1867
and block_id+blocks >= 1867;

TABLESPACE_NAME
——————————
USERS

SQL>  alter table test move ;

Table altered.

SQL> select TABLESpace_name from dba_free_space where FILE_ID=4 and BLOCK_ID <=1867 and block_id+blocks >= 1867;

no rows selected
SQL> select SEGMENT_NAME,SEGMENT_TYPE from dba_extents where FILE_ID=4 and BLOCK_ID <=1867 and block_id+blocks >= 1867;
SEGMENT_NAME              SEGMENT_TYPE
————————- ——————
TEST                      TABLE

Good, now the corrupted block is with in an extent.  I just droped the table as Oracle was successful in re-formating the block and created my TEST table on this block.

SQL> drop table test;

Table dropped.

Now I am good to go with the backup, and my copy went successfull.

RMAN> backup INCREMENTAL LEVEL 0 as copy datafile ‘/oradata/bmk/bmk/users01.dbf’  format ‘/oradata/bmk/dbcopy/users01.dbf’;

Starting backup at 14-DEC-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile copy
input datafile file number=00004 name=/oradata/bmk/bmk/users01.dbf
output file name=/oradata/bmk/dbcopy/users01.dbf tag=TAG20101214T145207 RECID=3 STAMP=737736736
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:15

Finished backup at 14-DEC-10

Article 0

$
0
0

ORA-04062: signature of package APPS.FND_DATE has been changed APP-FND-01926


error.png (673×213)

Solution :
=======

Oracle Doc ID 1442096.1

There is a de-synchronization in the time stamps between the package FND_DATE
and the program that called it so you need to re-synchronize all.

To implement the solution, please execute the following steps:

Stop your Midle Tier Services : adstpall.sh

1. Stop/restart the database.

2. Recreate the APPS.FND_DATE package:
From Uinx with applmgr user
cd $FND_TOP/patch/115/sql
sqlplus apps/… @AFDDATES.pls
sqlplus apps/… @AFDDATEB.pls

3. Run adadmin / Compile Apps Schema.

4. Restart your middle Tier Services : Retest the issue.

From RFC 2068 Hypertext Transfer Protocol - HTTP/1.1

$
0
0
Issue:

In R12.2.5, User trying to do export from forms, and he was hit by below error.

From RFC 2068 Hypertext Transfer Protocol - HTTP/1.1
10.4.5.404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.


If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.



Solution:

In RUN edition, Compile all JSP and restart the Middleware.

perl ojspCompile.pl --compile --flush -p 2

-p 2 (Number of parallel processes)

cd $ADMIN_SCRIPTS_HOME

Stop:
./admanagedsrvctl.sh stop oacore_server1
./admanagedsrvctl.sh stop oacore_server2
./adapcctl.sh stop

Start:
./adapcctl.sh start
./admanagedsrvctl.sh start oacore_server1
./admanagedsrvctl.sh start oacore_server2

Article 0

$
0
0

 ORA-19625 will encounter when the archives are obsolete.

Description:

There has been a major crash in the storage. A RAID volume failed and then we created those mount point again. The oracle DB was restored from RMAN backup, but after that we are facing challenges to take both hot and cold backup using RMAN . 

Look for all the following:

I find below error.




Above error ORA-19625 will encounter when the archives are obsolete or when expired means (physically not there in your location).

So what next run and see whether that archive are there in your archive location are not.
Database with a recovery catalog.
$ Export ORACLE_SID=<instance name>
$ Rman
RMAN> connect target /
RMAN> crosscheck archivelog all;
RMAN>delete expired archivelog all;
Then also no use I encountered same above error when I run hot backup script.

RMAN> exit

Workaround:

Connect through catalog and to repeat the same above steps.

$ rman target sys/<password>@<tnssevice> catalog <user>/<pwd>@<tnssevice>
Why above step required ?
Previously we delete expired logs from target machine but from catalog control file still there.
That’s the reason I connected to target and catalog
RMAN> crosscheck archivelog all;
RMAN> delete expired archivelog all;
RMAN>exit
Now issue resolved.

Article 1

$
0
0
ERROR:-  ORA-27154, ORA-27300, ORA-27301 & ORA-27302

After rebooting one cluster node, ASM instance came up fine but database instance failed with:

SYS@xxxx > startup nomount
ORA-27154: post/wait create failed
ORA-27300: OS system dependent operation:semget failed with status: 28
ORA-27301: OS failure message: No space left on device
ORA-27302: failure occurred at: sskgpcreates


The semaphore settings caused problems.
It turned out the kernel settings were insufficient. 

Solution:

cat /etc/sysctl.conf
kernel.sem = 250 32000 100 128

This line needs to be changed to:

kernel.sem = 250 32000 100 256

Note the change of the last number from 128 to 256.

After that applying the settings is done as root with:

sysctl -p

After that  instances came up just fine.

SYS@MRA> startup nomount
ORACLE instance started.
 Total System Global Area 1536602112 bytes
Fixed Size                  2253504 bytes
Variable Size             905973056 bytes
Database Buffers          620756992 bytes
Redo Buffers                7618560 bytes
SYS@MRA>

Article 0

$
0
0
Oracle Applications R12.2 Installation "ERROR : Cannot patch 10.1.2 Tools" during installation at 46% : -- Refernce Doc ID - 2100070.1

Installing 10.1.2 Tools patches.
Using /u01/oracle/DEV/fs2/inst/apps/DEV_r12dev/temp/xmldocs/instToolPatches.xml
Executing command: /OracleFiles/startCD/Disk1/rapidwiz/jre/Linux_x64/1.6.0/bin/java -cp /u01/oracle/DEV/fs2/inst/apps/DEV_r12dev/temp/ASInstallHome/fnd/../j11067592_fnd.zip:/u01/oracle/DEV/fs2/inst/apps/DEV_r12dev/temp/ASInstallHome/fnd/java/3rdparty/stdalone/xmlparserv2.zip -Doracle.apps.fnd.txk.env_home=/u01/oracle/DEV/fs2/EBSapps/appl/admin/DEV_r12dev/ -Doracle.apps.fnd.txk.runtime.config=/u01/oracle/DEV/fs2/inst/apps/DEV_r12dev/temp/xmldocs/instToolPatches.xml oracle.apps.fnd.txk.config.InstallService
Fatal Error: TXK Install Service
oracle.apps.fnd.txk.config.ProcessStateException: FileSys OS COMMAND Failed : Exit=2 See log for details. CMD= make -f ins_forms.mk sharedlib install ## Node=NodeId=1232 Type=24 TypeName=filesys_patch_action Name= RefId=457 State=init ConfigDoc=APPS_C_HOME ParentDoc=null Topology=R12 Action=os_cmd
at oracle.apps.fnd.txk.config.FileSysPatchActionNode.doFileSysOSCmd(FileSysPatchActionNode.java:169)
at oracle.apps.fnd.txk.config.FileSysPatchActionNode.processState(FileSysPatchActionNode.java:101)
at oracle.apps.fnd.txk.config.PatchActionNode.processState(PatchActionNode.java:187)
at oracle.apps.fnd.txk.config.PatchNode.processState(PatchNode.java:338)
at oracle.apps.fnd.txk.config.PatchesNode.processState(PatchesNode.java:79)
at oracle.apps.fnd.txk.config.InstallNode.processState(InstallNode.java:68)
at oracle.apps.fnd.txk.config.TXKTopology.traverse(TXKTopology.java:594)
at oracle.apps.fnd.txk.config.InstallService.doInvoke(InstallService.java:224)
at oracle.apps.fnd.txk.config.InstallService.invoke(InstallService.java:237)
at oracle.apps.fnd.txk.config.InstallService.main(InstallService.java:291)
Cannot patch 10.1.2 Tools.
RW-50010: Error: - script has returned an error: 1
RW-50004: Error code received when running external process. Check log file for details.
Running APPL_TOP Install Driver for DEV instance

Cause:

Verify the rpm glibc-devel*i686

rpm -qa --qf "%{n}-%{v}-%{r}.%{arch}\n" | grep glibc-devel-*.i686


Solution:

-The package RPM glibc-devel-2.17-55.el6.i686.rpm is required
-Install 'glibc-devel-2.17-55.el6.i686.rpm' (32-bit) or higher version.



ORA-02020: too many database links in use - Issue

$
0
0
select * from dual@<dblink>  
            *
ERROR at line 1:
ORA-02020: too many database links in use

Check the

APPTest@WWITest> show parameter open_links;

NAME                                 TYPE                              VALUE
------------------------------------ --------------------------------- ------------------------------
open_links                           integer                           4
open_links_per_instance              integer                           4


Note: Current session having the defalt value due to that this seesion exceeded the value.

To avoid this error.

Step 1:

SQL> alter system set open_links_per_instance=20 scope=spfile;
SQL> alter system set open_links=20 scope=spfile;

Step 2:

Restart the db

Step 3:

APPTest@WWITest> show parameter open_links;

NAME                                 TYPE                              VALUE
------------------------------------ --------------------------------- ------------------------------
open_links                           integer                           20
open_links_per_instance              integer                           20


Step 4:

APPTest@WWITest>  select * from dual@<db link>;

DUM
---
X

Note: Do not set it too high, it is better for the application to close database links when no longer in use than to change the parameter to a high number.



To close the unwanted db link:

APPTest@WWITest>  select in_transaction, count(*) from v$dblink group by in_transaction;

no row selected.

Note: if any transation is there in the db link you can close the db link by issuing the below command.

APPTest@WWITest>  alter session close database link <db link name>;

session altered.

OR
APPTest@WWITest>  exec DBMS_SESSION.CLOSE_DATABASE_LINK (<db link name>);

Article 2

$
0
0
                                 
                                      Commands to check the OS services in SOLARIS 10



Service Management Facility(SMF)

The Service Management Facility (SMF) is a core component of the new Predictive Self-Healing set of technologies introduced in Solaris 10. With SMF, system administrators can use simple command line utilities to easily identify, observe, and manage both the services provided by the system and the system itself.


SMF has a limited yet powerful set of commands. Each command has several options which cover the tasks required to manage Solaris systems. The following table lists the SMF commands.

Command   -  Description





svcs        -      Reports service status

svcadm  -     Used for service management: e.g., starting, stopping and restoring services


EXAMPLE:
my-system# svcs -a

STATE         STIME      FMRI
legacy_run    Apr_18     lrc:/etc/rcS_d/S51installupdates
legacy_run    Apr_18     lrc:/etc/rc2_d/S47pppd
legacy_run    Apr_18     lrc:/etc/rc2_d/S99audit
legacy_run    Apr_18     lrc:/etc/rc3_d/S76snmpdx
legacy_run    Apr_18     lrc:/etc/rc3_d/S90samba
disabled      Apr_18     svc:/network/ipfilter:default
disabled      Apr_18     svc:/network/rpc/keyserv:default
disabled      Apr_18     svc:/network/rpc/nisplus:default
disabled      Apr_18     svc:/application/print/server:default
disabled      Apr_18     svc:/network/dhcp-server:default
disabled      Apr_18     svc:/network/http:apache2
online        Apr_18     svc:/system/svc/restarter:default
online        Apr_18     svc:/network/pfil:default
online        Apr_18     svc:/network/physical:default
online        Apr_18     svc:/system/identity:domain
online        Apr_18     svc:/system/cryptosvc:default
online        Apr_18     svc:/network/inetd:default
online        Apr_18     svc:/network/telnet:default
online        Apr_18     svc:/network/ssh:default
online        Apr_18     svc:/system/zones:default
online        Apr_18     svc:/network/nfs/nlockmgr:default
offline       Apr_18     svc:/application/print/ipp-listener:default
offline       Apr_18     svc:/application/print/rfc1179:default


Displaying Individual Services

my-system# svcs -a |grep ftp
online         Jan_10   svc:/network/ftp:default


1   my-system# svcadm enable apache2
2      
3                   To display its status, use the svcs command:

4             my-system# svcs http
5                   STATE       STIME     FMRI
   online      11:26:46  svc:/network/http:apache2

Similarly we can disable and restart the services. 








Article 1

$
0
0
       Report Compilation Fails With Error "There was an error trying to initialize the HPI library"



Active users completed with the following error after upgrade or clone in solaris,

Error: 
-------
While compiling Reports (.rdf files) through <10.1.2 ORACLE_HOME>/bin/rwconverter, following error is thrown:           

As a result, rwconverter failed to generate the report.

There was an error trying to initialize the HPI library. 
Please check your installation, HotSpot does not work correctly 
when installed in the JDK 1.2 Solaris Production Release, or 
with any JDK 1.1.x release. 
Error occurred during initialization of VM 
Signal chaining not allowed for VM interrupt signal, try -Xusealtsigs.


Solution:
-----------

To implement the solution, please execute the following steps:

1. Rename/Backup the file "<10.1.2 ORACLE_HOME>/jdk/jre/lib/sparc/libjvm.so" if exists.

2. Create a soft link "<10.1.2 ORACLE_HOME>/jdk/jre/lib/sparc/libjvm.so" pointing to file "<10.1.2 ORACLE_HOME>/jdk/jre/lib/sparc/client/libjvm.so" - 

         2.1. Change directory to "<10.1.2 ORACLE_HOME>/jdk/jre/lib/sparc"

         2.2. Execute the command "ln -s client/libjvm.so libjvm.so"

3. Retest the issue                           

4. Migrate the solution to appropriate environment.



Now the active user will complete normal as Library file is updated after clone or upgrade.


Article 0

$
0
0
                       Oracle forms 10g installation, FRM-18108


After installation of oracle forms 10g, when we try to connect the form builder the following error is pop-out
FRM-18108: Failed to load the following objects.

ERROR
FRM-18108: Failed to load the following objects
.
Source Module: APPSTAND Source Object: STANDARD_PC_AND_VA
Source Module: APPSTAND Source Object: STANDARD_TOOLBAR
Source Module: APPSTAND Source Object: STANDARD_CALENDAR


SOLUTION:

- Copy the resource folder to local forms folder  from $AU_TOP(appl_top/au/forms/US/12.0.0//forms/US) and APPSTAND.fmb form in to the resource folder on the local forms server
- template.fmb file outside the resource folder

- And right click the form builder and change the start-in location pointing to local resource folder.(where resource folder and template.fmb is saved)

- Open the Form Builder, First open that APPSTAND.fmb and template.fmb Form , Now You try to Open the form.

- FRM-18108: Error will not come.


You can connect to the template.fmb form to testing purpose and if it is connecting your FRM-18108: Error will not come.

Article 2

$
0
0
ERROR: - "ORA-01092: ORACLE instance terminated. Disconnection forced".


Problem:- 

Once database open after within few seconds we got the

ERROR: - "ORA-01092: ORACLE instance terminated. Disconnection forced"

Alert log file shows lot of trace file and majorly shows

TRACE file:-

_smon_1596.trc:
ORA-00600: internal error code, arguments: [kdoirp-1], [2], [], [], [], [], [], []


Cause:-

To shrinking table data  & Rebuild the indexes related to that table at same time and unexpectedly database bounced by some client dba.


Solution:-

Start the database and immediately run the segments status.

 SQL> Select    segment_name,   status from dba_rollback_segs where status='NEEDS RECOVERY';

SEGMENT_NAME                   STATUS
------------------------            ----------------
_SYSSMU41$                     NEEDS RECOVERY
_SYSSMU100$                    NEEDS RECOVERY


So some segments need to recovery, then offline the those segments into parameter level and start the database

Keep the below parameter into pfile

*._offline_rollback_segments=_SYSSMU41$
*._offline_rollback_segments=_SYSSMU100$

And start the database using pfile. Then database successfully started and stable.

Then create spfile from pfile& shutdown database and startup.




Article 1

$
0
0

How  to  stop the datapump running job and how to reattach / resume same job:-



One of the main advantage of datapump is you can suspend the running export or import job and it can be resume if needed. Suppose if your server load is high when you started the export job, you can suspend the job and later you can resume the job once the server load comes down

The ability to detach from and reattach to long-running jobs without affecting the job itself. This allows DBAs and other operations personnel to monitor jobs from multiple locations. The Data Pump Export and Import utilities can be attached to only one job at a time.


To check the master control process table details.

$ sqlplus "/ as sysdba"

SQL*Plus: Release 11.2.0.4.0  - Production on
Copyright (c) 1982, 2008, Oracle.  All rights reserved.

 Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

Sql> Select * from dba_Datapump_job;

no rows selected

] $ expdp dumpfile=full1.dmp logfile=user.log directory=dp full=y
Username: system/xxxxxxx

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

Sql prompt and check the master control process:

$ sqlplus "/ as sysdba"

SQL*Plus: Release 11.2.0.4.0  - Production on
Copyright (c) 1982, 2008, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

Sql> SELECT owner_name, job_name, operation, job_mode, state FROM dba_datapump_jobs;

OWNER_NAME      JOB_NAME                OPERATION   JOB_MODE       STATE
---------------------- --------------------------------------------- ---------------------
EXPORT          SYS_EXPORT_FULL_02     SYSTEM            FULL         EXECUTING

Sql>  select SID,SERIAL# ,OPNAME,SOFAR,TOTALWORK,to_char(START_TIME,'dd-mon-yy hh:mi') Start_time,to_char(LAST_UPDATE_TIME,'dd-mon-yy hh:mi') Last_updated,time_remaining from  gv$session_longops where SOFAR<TOTALWORK;

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

To stop the data pump job:-

] $ ] $ expdp dumpfile=full1.dmp logfile=user.log directory=dp full=y
Username: system/xxxxxxx

Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/PASSWORD_HISTORY
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE


Once you press ^C on the expdp window it will come to interactive mode with
Export> prompt. In that prompt you can give commands to stop_job


Press CTRL+C on export window.
Export> stop_job
Prompt: - Y

Note:- STOP_JOB interactive command, the master table is retained for use in restarting the job.

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

Go to sqlplus window and check the master control process
Sql> SELECT owner_name, job_name, operation, job_mode, state FROM dba_datapump_jobs;

OWNER_NAME      JOB_NAME                OPERATION   JOB_MODE      STATE
---------------------- --------------------------------------------- ---------------------
EXPORT          SYS_EXPORT_FULL_02     SYSTEM            FULL     NOT RUNNING

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

To reattach / resume same data pump job:-

] $ expdp system/xxxxxx attach=SYS_EXPORT_FULL_02

Using the below mentioned command you can resume the job. Once you fire the below command in the prompt, expdp will load the job details and come "export>" prompt. You have to give continue_client command to resume the job.

Export> start_job
Export> continue_client

Export: Release 11.2.0.4.0 - 64bit Production on
Copyright (c) 2003, 2007, Oracle.  All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

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

SQLPLUS prompt

Sql> SELECT owner_name, job_name, operation, job_mode, state FROM dba_datapump_jobs;

OWNER_NAME      JOB_NAME                OPERATION   JOB_MODE       STATE
---------------------- --------------------------------------------- ---------------------
EXPORT          SYS_EXPORT_FULL_02     SYSTEM            FULL        EXECUTING

Query to create user and assign the responsibility for the existing User

$
0
0
DECLARE
v_user_name VARCHAR2 (100) := upper('&Enter_User_Name');
v_description VARCHAR2 (100) := 'New User';
 v_app_short_name VARCHAR2 (100);
 v_resp_key VARCHAR2 (100);
 CURSOR user_cur IS
 select a.application_short_name, r.responsibility_key
 from fnd_responsibility_vl r, fnd_application_vl a where
 r.application_id =a.application_id
 and R.responsibility_ID IN (SELECT RESPONSIBILITY_ID FROM fnd_user_resp_groups WHERE USER_ID=&from_userid AND END_dATE IS NULL);
user_rec user_cur%ROWTYPE;
BEGIN
 fnd_user_pkg.createuser
(x_user_name => v_user_name,
 x_owner => NULL,
 x_unencrypted_password => '&input_password',
 x_session_number => 0,
 x_start_date => SYSDATE,
 x_end_date => NULL,
 x_last_logon_date => NULL,
 x_description => v_description,
 x_password_date => NULL,
 x_password_accesses_left => NULL,
 x_password_lifespan_accesses => NULL,
 x_password_lifespan_days => NULL,
 x_employee_id => NULL,
 x_email_address => NULL,
 x_fax => NULL,
 x_customer_id => NULL,
 x_supplier_id => NULL,
 x_user_guid => NULL,
 x_change_source => NULL
 );
 COMMIT;
 OPEN user_cur;
 LOOP
 FETCH user_cur INTO user_rec;
 EXIT WHEN user_cur%NOTFOUND;
 fnd_user_pkg.addresp(username => v_user_name
 ,resp_app => user_rec.application_short_name
 ,resp_key => user_rec.responsibility_key
 ,security_group => 'STANDARD'
 ,description => NULL
 ,start_date => SYSDATE
 ,end_date => null);
 END LOOP;
 CLOSE user_cur;
commit;
END;
/

ORA-27154, ORA-27300, ORA-27301, ORA-27302

$
0
0
Facing the below error while startup / startup nomount?

Error:

ORA-27154: post/wait create failed

ORA-27300: OS system dependent operation:semget failed with status: 28

ORA-27301: OS failure message: No space left on device

ORA-27302: failure occurred at: sskgpcreates



Solution:


cat /etc/sysctl.conf

kernel.sem = 250 32000 100 120

Increase the above highlighted kernel.sem value to an higher like 200 or 256



Done!!!
 

ERR-3331 This page was already submitted and can not be re-submitted while importing your application.

$
0
0

ERROR:

ERR-3331 This page was already submitted and can not be re-submitted while importing your application.

CAUSE:
This is caused by the OHS (Oracle HTTP Server / Apache ) timing out.

SOLUTION:

To avoid having this error, simply change the OHS configuration. In the httpd.conf file located in your Apache/conf directory and increase the Timeout parameter.

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300
#Timeout 60

Document for changing the ip address of forms and reports in cloned server

$
0
0
Document for changing the ip address of forms and reports in cloned server
-----------------------------------------------------------------------------------------------------
1.Change ip in nodemanager.properties file
location:D:\u01\app\oracle\product\12.2.1\user_projects\domains\base_domain\nodemanager

2.Change the ip address in below locations
D:\u01\app\oracle\product\12.2.1\forms\templates\config\forms.conf
D:\u01\app\oracle\product\12.2.1\reports\conf\reports_ohs.conf
D:\u01\app\oracle\product\12.2.1\user_projects\domains\base_domain\config\fmwconfig\components\OHS\instances\ohs1\moduleconf\forms.conf
D:\u01\app\oracle\product\12.2.1\user_projects\domains\base_domain\config\fmwconfig\components\OHS\instances\ohs1\moduleconf\reports_ohs.conf

3.Change the ip address in below location
D:\u01\app\oracle\product\12.2.1\user_projects\domains\base_domain\config
FILE NAME:config.xml
(NOTE:Here you will have to change from old ip to new ip
Here there will be a ip in three places you should change in all the three places you can find it by ctr+F)

4.Finally start all the services
D:\u01\app\oracle\product\12.2.1\user_projects\domains\base_domain\bin\startNodeManager.cmd
D:\u01\app\oracle\product\12.2.1\user_projects\domains\base_domain\bin\startWebLogic.cmd
D:\u01\app\oracle\product\12.2.1\user_projects\domains\base_domain\bin\startManagedWebLogic.cmd WLS_FORMS
D:\u01\app\oracle\product\12.2.1\user_projects\domains\base_domain\bin\startmanagedWebLogic.cmd WLS_REPORTS
-----------------------------------------------------------------------------------------------------------------------------


Viewing all 1640 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>