Below is the syntax to create database directory
SQL> create directory PLSQL_DIR AS ‘/oratmp/code’;
Directory created.
Grant Read/write privileges to Required Schema
SQL> GRANT READ,WRITE ON DIRECTORY PLSQL_DIR TO APPS;
Grant succeeded.
I was trying to restore database using RMAN Backup
RMAN-00571: ===========================================================
RMAN-00569: ===============
ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command
RMAN-05501: aborting duplication of target database
RMAN-03009: failure of allocate command on ORA_AUX_SBT_TAPE_1 channel
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information:
Cause: Backup Configuration was modified.
Solution:
Use the below command to Resolve the error and continue with Database Restore
rman auxiliary /
run
{
allocate auxiliary channel c1 type disk;
allocate auxiliary channel c2 type disk;
duplicate database to ‘DEV’ backup location ‘/Daily_Backup/Backup_16042018’;
}
exit;
EOF
Step 2: Verify if the database sessions are active/Inactive at the database level using the below query.
select inst_id,sid,serial#,program,module,status,last_call_et,sql_id from gv$session where sid=&sid;
— sid value to be taken from output of Sql Query in Step 1
If Database session is INACTIVE And Running no sql for more than an Hour, we can Terminate the Concurrent Requests.
If the Database session is ACTIVE and has an SQL_ID attached with it, Need to check on tuning the sql being run by the database session.
I will cover more details about SQL Tuning in another post.
Steps to modify Workflow system administrator role in Oracle EBS 11i/R12
Oracle Workflow System Administrator can be changed in below ways.
1.update wf_resources set text=’&Enter_Admin_Name’ where name=’WF_ADMIN_ROLE’;
e.g
update wf_resources set text=’FND_RESP1:20420′ where name=’WF_ADMIN_ROLE’;
2. Change the value of Context file parameter s_wf_admin_role and run Autoconfig
$ cat $CONTEXT_FILE|grep wf_admin
<username oa_var=”s_wf_admin_role” customized=”yes”>SYSADMIN</username>
3. Change it from Workflow Administrator Web Applications responsibility (Login as sysadmin >> Workflow Administrator Web Applications >> Administration
[Note: Ensure that context file parameter “s_wf_admin_role” is updated with modified value to preserve changes during autoconfig Run]
4. adop phase=finalize
5. adop phase=cutover
6. adop phase=cleanup
3.Deployment of EBS Plugin for Oracle Enterprise Manager OEM 13c
[EBS Plug-in Deployment to be implemented on OMS Agent node and on all EBS Nodes where EM Monitoring is Required]
3.1 Deploy EBS Plugin to OMS Agent
Login to Oracle Enterprise Manager OEM console to deploy plugin to OMS Agent
Go to Setup => Extensibility => Plug-ins:
Select Oracle E-business Suite and Click Deploy-On
Provide the Required details and proceed.
[OMS Restart Required for this activity- Implemented through console]
Monitor the deployment status using below command
emctl status oms -details
3.2 Deploy Plug-in to Management Agent
The process is similar to the deployment procedure to the OMS Agent, but in this case the EBS host targets must be selected.
[Note: Add new management agents for EBS Targets if not already available.]
Steps for Database restore using Oracle Recovery Manager (RMAN)
1.Connect to target database
Startup the Target database in Nomount stage
SQL> Startup nomount
2.Run the below Command to Restore Oracle database using RMAN
rman auxiliary /
run
{
duplicate database to ‘DEV’ backup location ‘/DB_BACKUP/Daily_Backup/daily_bkp_04102018’;
}
Where DEV is the target instance for Restore
Backup Location – Directory where RMAN backup is located
3. Verify that Oracle database is up and running.
Solution
Contact your Network admin to allow access to 1433 using Servername (MSSQLDB)
(or)
Change the below configuration
1. Set Oracle Home to point to your Gateway Oracle HOME
2. Navigate to $ORACLE_HOME/dg4msql/admin
Change below values in initdg4msql.ora
changed HS_FDS_CONNECT_INFO from MSSQLDB to IP address
#
HS_FDS_CONNECT_INFO=10.x.x.x:1433//wfcdb
# alternate connect format is hostname/serverinstance/databasename
HS_FDS_TRACE_LEVEL=OFF
HS_FDS_RECOVERY_ACCOUNT=RECOVER
HS_FDS_RECOVERY_PWD=RECOVER
3. Restart the listener in Gateway Oracle HOME
4. Verify the database link is working fine.
SQL>select sysdate from dual@DBLINK_MSSQL;
==>Above Query should return current system date.