[oracle@oracleagent:Database] opatch apply
Oracle Interim Patch Installer version 12.2.0.1.27
Copyright (c) 2022, Oracle Corporation. All rights reserved.
Oracle Home : /u01/app/oracle/product/12.1.0
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/12.1.0/oraInst.loc
OPatch version : 12.2.0.1.27
OUI version : 12.1.0.2.0
Logfile location: /u01/app/oracle/product/12.1.0/cfgtoollogs/opatch/opatch2022-01-21_08-04-36AM_1.log
Verifying environment and performing prerequisite checks… Prerequisite check “CheckActiveFilesAndExecutables” failed. The details are:
Following active executables are not used by opatch process : /u01/app/oracle/product/12.1.0/lib/libclntsh.so.12.1
Following active executables are used by opatch process :
[oracle@oracleagent:Database] /sbin/fuser /u01/app/oracle/product/12.1.0/lib/libclntsh.so.12.1 /u01/app/oracle/product/12.1.0/lib/libclntsh.so.12.1: 22235m 24173m
[oracle@oracleagent:Database] kill -9 22235 24173
[oracle@oracleagent:Database] opatch apply
Oracle Interim Patch Installer version 12.2.0.1.27
Copyright (c) 2022, Oracle Corporation. All rights reserved.
Oracle Home : /u01/app/oracle/product/12.1.0
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/12.1.0/oraInst.loc
OPatch version : 12.2.0.1.27
OUI version : 12.1.0.2.0
Logfile location: /u01/app/oracle/product/12.1.0/cfgtoollogs/opatch/opatch2022-01-21_08-08-33AM_1.log
Verifying environment and performing prerequisite checks…
OPatch continues with these patches: 32768233 33128590
Do you want to proceed? [y|n]
y
User Responded with Y
All checks passed.
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = ‘/u01/app/oracle/product/12.1.0’)
Is the local system ready for patching? [y|n]
y
User Responded with Y
Backing up files…
Applying sub-patch ‘32768233’ to OH ‘/u01/app/oracle/product/12.1.0’
ApplySession: Optional component(s) [ oracle.network.cman, 12.1.0.2.0 ] not present in the Oracle Home or a higher version is found.
…..
….
…..
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
7. scan and list the disk using oracleasm: [root@asm dev]# oracleasm scandisks Reloading disk partitions: done Cleaning any stale ASM disks… Scanning system for ASM disks… [root@asm dev]# oracleasm listdisks DISK1 DISK2 [root@asm dev]#
8. asmcmd tool:
[oracle@asm ~]$ asmcmd ASMCMD> ASMCMD>
I. list the disk group ASMCMD> lsdg State Type Rebal Sector Logical_Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name MOUNTED EXTERN N 512 512 4096 4194304 30712 25860 0 25860 0 N DATA/ ASMCMD>
II. list datafile,controlfile
ASMCMD> cd DATA/ ASMCMD> ls ASM/ ORAASM/ orapwasm ASMCMD> cd ORAASM ASMCMD> ls 86B637B62FE07A65E053F706E80A27CA/ CONTROLFILE/ D47CB418C2B91B66E053867EA8C0C5A0/ D47CEAB72C2F2513E053867EA8C0538D/ DATAFILE/ ONLINELOG/ PARAMETERFILE/ TEMPFILE/ ASMCMD> cd DATAFILE ASMCMD> ls SYSAUX.258.1092813853 SYSTEM.257.1092813819 UNDOTBS1.259.1092813869 USERS.260.1092813869 ASMCMD> pwd +DATA/ORAASM/DATAFILE ASMCMD>
9. check css,has status:
[oracle@asm ~]$ crsctl check has CRS-4638: Oracle High Availability Services is online [oracle@asm ~]$ crsctl check css CRS-4529: Cluster Synchronization Services is online [oracle@asm ~]$
10. check has version:
[oracle@asm ~]$ crsctl query has releaseversion Oracle High Availability Services release version on the local node is [19.0.0.0.0] [oracle@asm ~]$ crsctl query has softwareversion Oracle High Availability Services version on the local node is [19.0.0.0.0] [oracle@asm ~]$
11. asmca —> GUI for create and manage diskgroup:
12. KFOD – discovering disks with the help of asm disk strings: KFED – discovering disk headers
13. check olr and ocr location : [oracle@asm ~]$ ocrcheck Status of Oracle Cluster Registry is as follows : Version : 4 Total space (kbytes) : 491684 Used space (kbytes) : 82368 Available space (kbytes) : 409316 ID : 786336035 Device/File Name : /u01/app/grid/cdata/localhost/local.ocr Device/File integrity check succeeded
Device/File not configured
Device/File not configured
Device/File not configured
Device/File not configured
Cluster registry integrity check succeeded
Logical corruption check bypassed due to non-privileged user
[oracle@asm ~]$ [oracle@asm ~]$ ocrcheck -local Status of Oracle Local Registry is as follows : Version : 4 Total space (kbytes) : 491684 Used space (kbytes) : 83496 Available space (kbytes) : 408188 ID : 476403298 Device/File Name : /u01/app/oracle/crsdata/asm/olr/asm_19.olr Device/File integrity check succeeded
Local registry integrity check succeeded
Logical corruption check bypassed due to non-privileged user
[oracle@asm ~]$ ocrcheck -local -config Oracle Local Registry configuration is : Device/File Name : /u01/app/oracle/crsdata/asm/olr/asm_19.olr [oracle@asm ~]$
14. Check the asm status in sysasm admin:
[oracle@asm ~]$ sqlplus / as sysasm
SQL*Plus: Release 19.0.0.0.0 – Production on Sun Jan 2 17:57:52 2022 Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle. All rights reserved.
Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production Version 19.3.0.0.0
15. check instance type:
SQL> show parameter INSTANCE_TYPE
NAME TYPE VALUE ———————————— ———– —————————— instance_type string ASM
16. spfile location:
SQL> show parameter spfile
NAME TYPE VALUE ———————————— ———– —————————— spfile string +DATA/ASM/ASMPARAMETERFILE/reg istry.253.1092745689
17. pfile creation: SQL> create pfile from spfile;
File created.
SQL> exit Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production Version 19.3.0.0.0 [oracle@asm ~]$ cd $ORACLE_HOME/dbs [oracle@asm dbs]$ ls ab_+ASM.dat hc_+ASM.dat init+ASM.ora init.ora [oracle@asm dbs]$ cat init+ASM.ora +ASM.__oracle_base=’/u01/app/oracle’#ORACLE_BASE set from in memory value .asm_diskstring=’/dev/oracleasm/disks’ .asm_power_limit=1 .large_pool_size=12M .remote_login_passwordfile=’EXCLUSIVE’ [oracle@asm dbs]$ sqlplus / as sysasm
SQL*Plus: Release 19.0.0.0.0 – Production on Sun Jan 2 18:01:05 2022 Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle. All rights reserved.
Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production Version 19.3.0.0.0
18. instance type and status:
SQL> select instance_name,status from v$instance;
INSTANCE_NAME STATUS —————- ———— +ASM STARTED
SQL> exit Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production Version 19.3.0.0.0 [oracle@asm dbs]$ crsctl stat res -t ——————————————————————————– Name Target State Server State details ——————————————————————————– Local Resources ——————————————————————————– ora.DATA.dg ONLINE ONLINE asm STABLE ora.LISTENER.lsnr ONLINE ONLINE asm STABLE ora.asm ONLINE ONLINE asm Started,STABLE ora.ons OFFLINE OFFLINE asm STABLE ——————————————————————————– Cluster Resources ——————————————————————————– ora.cssd 1 ONLINE ONLINE asm STABLE ora.diskmon 1 OFFLINE OFFLINE STABLE ora.evmd 1 ONLINE ONLINE asm STABLE ora.oraasm.db 1 ONLINE ONLINE asm Open,HOME=/u01/app/o racle/product/19.0.0 /dbhome_1,STABLE ——————————————————————————– [oracle@asm dbs]$
19. ASMCMD check datafile and controlfile:
[oracle@asm dbs]$ asmcmd ASMCMD> ASMCMD> ASMCMD> ASMCMD> lsdg State Type Rebal Sector Logical_Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name MOUNTED EXTERN N 512 512 4096 4194304 30712 25852 0 25852 0 N DATA/ ASMCMD> cd +DATA/oraasm/datafile ASMCMD> ls SYSAUX.258.1092813853 SYSTEM.257.1092813819 UNDOTBS1.259.1092813869 USERS.260.1092813869 ASMCMD> ls -l Type Redund Striped Time Sys Name DATAFILE UNPROT COARSE JAN 02 17:00:00 Y SYSAUX.258.1092813853 DATAFILE UNPROT COARSE JAN 02 17:00:00 Y SYSTEM.257.1092813819 DATAFILE UNPROT COARSE JAN 02 17:00:00 Y UNDOTBS1.259.1092813869 DATAFILE UNPROT COARSE JAN 02 17:00:00 Y USERS.260.1092813869 ASMCMD>
ASMCMD> cd +DATA/oraasm/parameterfile
ASMCMD> ls -l Type Redund Striped Time Sys Name PARAMETERFILE UNPROT COARSE JAN 02 17:00:00 Y spfile.274.1092815069 ASMCMD>
ASMCMD> ls -l Type Redund Striped Time Sys Name ASMPARAMETERFILE UNPROT COARSE DEC 31 12:00:00 Y REGISTRY.253.1092745689 ASMCMD> pwd +DATA/ASM/ASMPARAMETERFILE ASMCMD>
20. query to check asm_disk and asm disk_group:
SQL> select disk_number,name,path,header_status,mode_status,state,total_mb,free_mb from v$asm_disk;
DISK_NUMBER NAME PATH HEADER_STATU MODE_ST STATE TOTAL_MB FREE_MB —————————————————————————————————- 0 DATA_0000 /dev/oracleasm/disks/DISK1 MEMBER ONLINE NORMAL 20476 17228
1 DATA_0001 /dev/oracleasm/disks/DISK2 MEMBER ONLINE NORMAL 10236 8624
SQL> select group_number,name,state,type from v$asm_diskgroup;
GROUP_NUMBER NAME STATE TYPE ———— —————————— ———– —— 1 DATA MOUNTED EXTERN
SQL>
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
1. Check the status of Notifications: ====================================
col RECIPIENT_ROLE format a20
col FROM_USER format a20
col TO_USER format a20
set lines 170
select NOTIFICATION_ID,MESSAGE_TYPE,MESSAGE_NAME,RECIPIENT_ROLE,STATUS,FROM_USER,TO_USER from wf_notifications where NOTIFICATION_ID=‘&1′;
2.Check the status of Workflow components: =========================================
SELECT component_name as Component, component_status as Status FROM fnd_svc_components
3. To check whether notification is present: =========================================
select recipient_role,notification_id,status,mail_status from wf_notifications where recipient_role like ‘&user_name’;
The e-mail notification is sent only if all of the following is true.
Notification status is OPEN or CANCELED
Notification mail_status is MAIL or INVALID
4. Check Recipient role has a valid e-mail address and notification preference MAIL% =========================================
SELECT email_address, nvl(WF_PREF.get_pref(name, ‘MAILTYPE’), notification_preference)
FROM wf_roles
WHERE name = ‘&recipient_role’;
Recipient can receive email notification only if
notification preference is not set ‘QUERY’ / ‘DISABLED’ / ‘SUMMARY’ / ‘SUMHTML’ &
recipient has valid email address
5.WF_DEFERRED Queue volume: ===========================
col corrid format a60
set lines 130
set pages 100
select NVL(substr(wfe.corrid,1,50),’NULL – No Value’) corrid, decode(wfe.state,0,’0 = Ready’,1,’1 = Delayed’,2,’2 = Retained’,
3,’3 = Exception’,to_char(substr(wfe.state,1,12))) State,count(*) COUNT
from applsys.wf_deferred wfe group by wfe.corrid, wfe.state;
6.WF_NOTIFICATION_OUT Queue volume: ===================================
col corrid format a60
set lines 130
set pages 100
select NVL(substr(wfe.corrid,1,50),’NULL – No Value’) corrid, decode(wfe.state,0,’0 = Ready’,1,’1 = Delayed’,2,’2 = Retained’,
3,’3 = Exception’,to_char(substr(wfe.state,1,12))) State,count(*)COUNT
from applsys.wf_notification_out wfe group by wfe.corrid, wfe.state;
Description: In this blog, we are going to see step by step process of oracle data guard manual switchover process physical standby to primary.
Switch Over: A switchover is a role reversal between the primary database and one of its standby databases. A switchover guarantees no data loss. This is typically done for planned maintenance of the primary system. During a switchover, the primary database transitions to a standby role, and the standby database transitions to the primary role. The transition occurs without having to re-enable either database.
Overall Steps:
1. Check Primary and Standby database role and open_mode.2. Change nls_date_format and check current log sync status.3. Check switch over status both primary and standby servers.4. Primary side switch over process.5. Standby side switch over process.6. Check the log sync status both sides.7. New primary database parameter configuration.8. Switch log files and check the log sync status.
Step 1:- Check primary and standby database role and open_mode.
SQL> select name,open_mode,database_role from v$database; Step 2:- Change nls_date_format and check current log sync status.
check the log sequence on both primary and standby sides. SQL> ALTER SESSION SET nls_date_format=’DD-MON-YYYY HH24:MI:SS’; Session altered. SQL> SELECT sequence#, first_time, next_time, applied FROM v$archived_log ORDER BY sequence#; Step 3:- Check switch over status both primary and standby servers. SQL> select switchover_status from v$database;
Step 4:- Primary side switch over process.
Switch over to standby. SQL> alter database commit to switchover to standby; Database altered. Bounce the database. SQL> shut immediate SQL> startup nomount Mount standby database. SQL> alter database mount standby database; Start MRP process. SQL> alter database recover managed standby database disconnect from session; Database altered. check the database role. SQL> select name,open_mode,database_role from v$database; Step 5:- Standby side switchover process:
Stop the MRP process. SQL> alter database recover managed standby database cancel; Database altered. Switch Over to Primary. SQL> alter database commit to switchover to primary; Database altered. Check database role changed or not and open_mode. SQL> select name,open_mode,database_role from v$database; Open the database. SQL> alter database open; Database altered. Check the database role and open_mode. SQL> select name,open_mode,database_role from v$database; Step 6:- Check the log sync status both sides. SQL> archive log list
Check both side log sync status.
Step 7:- New primary database parameter configuration for log sync. SQL> alter system set log_archive_dest_1 =’location=use_db_recovery_file_dest valid_for=(all_logfiles,all_roles) db_unique_name=local’ scope=spfile; System altered.
SQL> alter system set log_archive_dest_2 =’service=cloud async valid_for=(online_logfiles,primary_role) db_unique_name=cloud’ scope=spfile; System altered.
SQL> alter system set db_file_name_convert=’/u01/app/oracle/oradata/LOCAL/datafile/’,’/u01/app/oracle/oradata/CLOUD/datafile/’ scope=spfile; System altered.
SQL> alter system set log_file_name_convert=’/u01/app/oracle/oradata/LOCAL/onlinelog/’,’/u01/app/oracle/oradata/CLOUD/onlinelog/’ scope=spfile; System altered.
SQL> ALTER SYSTEM SET log_archive_config=’dg_config=(local,cloud)’ SCOPE=both; System altered.
SQL> ALTER SYSTEM SET fal_server=’cloud’ SCOPE=both; System altered.
SQL> ALTER SYSTEM SET fal_client=’local’ SCOPE=both; System altered.
SQL> select DEST_NAME,STATUS,ERROR from v$ARCHIVE_DEST where status!=’INACTIVE’; DEST_NAME ——————————————————————————– STATUS ERROR ——— —————————————————————– LOG_ARCHIVE_DEST_1 VALID Step 8:-Switch log files and check the log sync status. Primary side switch logfiles: enable log_archive_dest_state_2. SQL> alter system switch logfile; SQL> archive log list Check log file sync status on standby side:- Restart the MRP process. SQL> alter database recover managed standby database cancel; Database altered. SQL> alter database recover managed standby database disconnect nodelay; Database altered. check log sync status. SQL> SELECT ARCH.THREAD# “Thread”, ARCH.SEQUENCE# “Last Sequence Received”, APPL.SEQUENCE# “Last Sequence Applied”, (ARCH.SEQUENCE# – APPL.SEQUENCE#) “Difference” FROM (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH, (SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL WHERE ARCH.THREAD# = APPL.THREAD# ORDER BY 1;
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Description: In this blog, we are going to see step by step process for adding a disk in ASM disk group.
Rebalance ASM Disks: Oracle ASM automatically rebalances disk groups when their configuration changes. You might want to do a manual rebalance operation to control the speed of what would otherwise be an automatic rebalance operation.
Pre request- Add needed disk space in virtual machine.
Steps:-
1. Login as root user source the bash profile:
[oracle@asm ~]$ . .bash_profile [oracle@asm ~]$ su root Password: [root@asm oracle]# [root@asm oracle]# cd
2. New disk configuration:
[root@asm ~]# fdisk /dev/sdd Welcome to fdisk (util-linux 2.23.2).
Changes will remain in memory only until you decide to write them. Be careful before using the write command.
The device does not contain a recognized partition table Building a new DOS disklabel with disk identifier 0xf8f5f5c6.
Command (m for help): m Command action a toggle a bootable flag b edit bsd disklabel c toggle the dos compatibility flag d delete a partition g create a new empty GPT partition table G create an IRIX (SGI) partition table l list known partition types m print this menu n add a new partition o create a new empty DOS partition table p print the partition table q quit without saving changes s create a new empty Sun disklabel t change a partition’s system id u change display/entry units v verify the partition table w write table to disk and exit x extra functionality (experts only)
Command (m for help): n Partition type: p primary (0 primary, 0 extended, 4 free) e extended Select (default p): Using default response p Partition number (1-4, default 1): First sector (2048-10485759, default 2048): Using default value 2048 Last sector, +sectors or +size{K,M,G} (2048-10485759, default 10485759): Using default value 10485759 Partition 1 of type Linux and of size 5 GiB is set
Command (m for help): w The partition table has been altered!
Calling ioctl() to re-read partition table. Syncing disks.
3. List the disks:
[root@asm ~]# fdisk -l
Disk /dev/sda: 107.4 GB, 107374182400 bytes, 209715200 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x0001d229
Device Boot Start End Blocks Id System /dev/sda1 * 2048 14338047 7168000 83 Linux /dev/sda2 14338048 98306047 41984000 83 Linux /dev/sda3 98306048 182274047 41984000 83 Linux /dev/sda4 182274048 209715199 13720576 5 Extended /dev/sda5 182276096 196612095 7168000 82 Linux swap / Solaris
Disk /dev/sdb: 21.5 GB, 21474836480 bytes, 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0xeba933f3
Device Boot Start End Blocks Id System /dev/sdb1 2048 41943039 20970496 83 Linux
Disk /dev/sdc: 10.7 GB, 10737418240 bytes, 20971520 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x330f95dd
Device Boot Start End Blocks Id System /dev/sdc1 2048 20971519 10484736 83 Linux
Disk /dev/sdd: 5368 MB, 5368709120 bytes, 10485760 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0xf8f5f5c6
Device Boot Start End Blocks Id System /dev/sdd1 2048 10485759 5241856 83 Linux
This will configure the on-boot properties of the Oracle ASM library driver. The following questions will determine whether the driver is loaded on the boot and what permissions it will have. The current values will be shown in brackets (‘[]’). Hitting <ENTER> without typing an answer will keep that current value. Ctrl-C will abort.
Default user to own the driver interface [oracle]: Default group to own the driver interface [oinstall]: Start Oracle ASM library driver on boot (y/n) [y]: Scan for Oracle ASM disks on boot (y/n) [y]: Writing Oracle ASM library driver configuration: done [root@asm ~]#
SQL*Plus: Release 19.0.0.0.0 – Production on Thu Jan 6 06:13:02 2022 Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle. All rights reserved.
Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production Version 19.3.0.0.0
7. Check the disk group status: SQL> set lines 999; col diskgroup for a15 col diskname for a15 col path for a35 select a.name DiskGroup,b.name DiskName, b.total_mb, (b.total_mb-b.free_mb) Used_MB, b.free_mb,b.path,b.header_status from v$asm_disk b, v$asm_diskgroup a where a.group_number (+) =b.group_number order by b.group_number,b.name;SQL> SQL> SQL> SQL> 2 3
DISKGROUP DISKNAME TOTAL_MB USED_MB FREE_MB PATH HEADER_STATU ————— ————— ———- ———- ———- ———————————– ———— 0 0 0 /dev/oracleasm/disks/DISK3 PROVISIONED DATA DATA_0000 20476 3380 17096 /dev/oracleasm/disks/DISK1 MEMBER DATA DATA_0001 10236 1676 8560 /dev/oracleasm/disks/DISK2 MEMBER
8. Create a disk in asm using rebalance method:
SQL> alter diskgroup DATA add disk ‘/dev/oracleasm/disks/DISK3’ NAME DISK3 rebalance power 100;
Diskgroup altered.
9. Check the status of new disk group its shown as RUN:
SQL> col ERROR_CODE for a10 col PASS for a10 select * from v$asm_operation;SQL> SQL>
10. Check after some time it will show no rows selected so it can be created fine:
SQL> select * from v$asm_operation; no rows selected
11. View the disk group:
SQL> set lines 999; col diskgroup for a15 col diskname for a15 col path for a35 select a.name DiskGroup,b.name DiskName, b.total_mb, (b.total_mb-b.free_mb) Used_MB, b.free_mb,b.path,b.header_status from v$asm_disk b, v$asm_diskgroup a where a.group_number (+) =b.group_number order by b.group_number,b.name;SQL> SQL> SQL> SQL> 2 3
DISKGROUP DISKNAME TOTAL_MB USED_MB FREE_MB PATH HEADER_STATU ————— ————— ———- ———- ———- ———————————– ———— DATA DATA_0000 20476 2884 17592 /dev/oracleasm/disks/DISK1 MEMBER DATA DATA_0001 10236 1456 8780 /dev/oracleasm/disks/DISK2 MEMBER DATA DISK3 5116 728 4388 /dev/oracleasm/disks/DISK3 MEMBER
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Output Post Processor (OPP) in Oracle Applications R12 and 11i
OPP runs as a service that can be managed through Oracle Applications Manager (OAM) from the System Activity page (Navigation: Applications Dashboard > Applications
Service (from the dropdown list) > Go).
How to Increase the number of Output Post Processors?
1.Log on to Applications with “System Administrator” responsibility.
2.Navigate to Concurrent -> Manager -> Define.
3. Query for the “Output Post Processor” service.
4. Click on “Work Shifts” and increase the number of processes
How to get OPP manager log file location?
$APPLCSF/log/<SID>/FNDOPP####.txt OR
1,System Administrator > Concurrent > Manager > Administer
2,Search for ‘Output Post Processor’
3,Click the ‘Processes’ button .
4, Click the Manager Log button. This will open the ‘OPP’
Upload the OPP log file.
In some cases, Output Post Processor is not starting up and it shows Actual and Target are showing different values when we query for Output Post Processor.
The log files show no error message. In this case, apply the following possible solution for starting the OPP.
1. Shut down the internal manager by using adcmctl.sh stop apps/apps
2. Make sure there are no FNDLIBR processes running:
$ ps -ef| grep FNDLIBR OR ps -ef|grep applprod|grep FNDLIBR
3. If there is any FNDLIBR process please kill it $ kill -9 pid
4. Run cmclean.sql script
5. Restart the internal manager by using adcmctl.sh start apps/apps
or How to kill and start Output Post Processor (OPP) Background:
This article explains how to kill OPP and restart the same
Solution:
1,System Administator > Concurrent > Manager > Administer
2,Query “Output Post Processor” -> Processes button
Get the sytem id of “Output Post Processor”
3,ps -ef|grep [system id]
4,kill -9 [system id] in Unix
5,System Administator > Concurrent > Manager > Administer
6,Query “Output Post Processor” -> Restart button
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Description: In this blog we are going to see datafile,logfile,and archivelog create,resize delete in the ASM oracle database server.
Oracle ASM:
Oracle ASM is a volume manager and a file system for Oracle database files that supports single-instance Oracle Database and Oracle Real Application Clusters (Oracle RAC) configurations. Oracle ASM is Oracle’s recommended storage management solution that provides an alternative to conventional volume managers, file systems, and raw devices.
ASM Disk Groups:
Oracle ASM uses disk groups to store data files; an Oracle ASM disk group is a collection of disks that Oracle ASM manages as a unit. Within a disk group, Oracle ASM exposes a file system interface for Oracle database files.
Check datafile logfile and archivelog location in ASM
SQL> select name from v$datafile; NAME ————————————————————————————————–
[applmgr@document appl]$ FNDCPASS apps/apps 0 Y system/ manager SYSTEM APPLSYS <new apps passwd>
FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS newpasswd
Start AdminServer using the $INST_TOP/admin/scripts/adadminsrvctl.sh
Note:Don’t start any other application tier services.
Change the “apps” password in WLS Datasource as follows:
Log in to WLS Administration Console. http://document.subnet.vcn.oraclevcn.com:8000/OA_HTML/AppsLogin
Click Lock & Edit in Change Center.
In the Domain Structure tree, expand Services, then select Data Sources.
On the “Summary of JDBC Data Sources” page, select EBSDataSource
On the “Settings for EBSDataSource” page, select the Connection Pool tab.
Enter the new password in the “Password” field.
Enter the new password in the “Confirm Password” field.
Click Save.
Check whether you are able to connect to DB using apps
sqlplus apps/<newpassword> from application tier.
Before Starting all the services. Run Autoconfig.
cd $ADMIN_SCRIPTS_HOME
sh adautocfg.sh
Now start the services.
Start all the application tier services using the
$INST_TOP/admin/scripts/adstrtal.sh script.
How to change the SYSADMIN password
[applmgr@document appl]$ FNDCPASS apps/*** 0 Y system/manager USER SYSADMIN new_password
What is Apps Schema?
Apps are a schema that does not contain any tables of itself. We can say APPS is the shared runtime schema for all E-Business Suite products. It contains all the synonyms of all the tables in Oracle apps. But it also contains packages, functions, procedures. The default password is apps.
What is Applsys Schema?
Applsys schema contains all the tables required for administrative purposes. The default password is apps. All the technical products’ database objects are consolidated into a single schema called Applsys
What is Applsyspub schema?
Applsyspub schema is responsible for password checking. The default password is pub.Applsyspub is used for authentication by having read-only views.
Why should Apps & Applsys passwords always be the same?
The need to have the same password for Apps and Applsys is because when you sign on to apps, initially it connects to a public schema called APPLSYSPUB. This validates the AOL username and password that we enter (operations/welcome using a guest user account. Once this is verified we select responsibility, this is validated by APPLSYS schema and then it connects to APPS schema.
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Generally in day to days usage of Oracle Apps R12, we came up with many issues which is resolved by bouncing Apache Server like:-
– JSP page not loading
– Changes are not appearing after done with personalization
– Some weird java error.
It is really easy to get this done.
[oraappl@apps-node-qa ~]$ . ./EBSapps.env Run
E-Business Suite Environment Information
RUN File System : /wwi/erp/apps/fs2/EBSapps/appl
PATCH File System : /wwi/erp/apps/fs1/EBSapps/appl
Non-Editioned File System : /wwi/erp/apps/fs_ne
Description: In this blog, we are going to see step by step process on the oracle data guard manual failover process.
Failover: A failover is a role transition in which one of the standby databases is transitioned to the primary role after the primary database fails or has become unreachable. A failover may or may not result in data loss depending on the protection mode in effect at the time of the failover.
Data Guard Configuration Details:- Overall Steps:-
1. Check the database role,open_mode in standby server.2. Cancel MRP process.3. Change Standby to Primary Database.4. Bounce the database.
Step 1:- Check the database role,open_mode in the standby server. SQL> select name,open_mode,database_role from v$database; NAME OPEN_MODE DATABASE_ROLE ——— ——————– —————- CLOUD MOUNTED PHYSICAL STANDBY
Cancel the MRP process: SQL> recover managed standby database cancel; Media recovery complete.
Finish the MRP process: SQL> alter database recover managed standby database finish; Database altered. Step 3:- Change Standby to Primary Database. SQL> alter database activate standby database; Database altered.
Check the role changed or not: SQL> select name,open_mode,database_role from v$database; NAME OPEN_MODE DATABASE_ROLE ——— ——————– —————- CLOUD MOUNTED PRIMARY Step 4:- Bounce the Database. SQL> shut immediate SQL> startup Check the database role and status. SQL> select name,open_mode,database_role from v$database; NAME OPEN_MODE DATABASE_ROLE ——— ——————– —————- CLOUD READ WRITE PRIMARY
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
