Clearing an Enterprise manager agent that fails to upload

This is the standard set of actions that I go through when I have problems with an EM agent that a stop/start/upload does not resolve

The two types of errors I generally see are

EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..

Starting agent …………………………… started but not ready.

Follow the steps below, which can be cut and pasted

export AGENT_HOME=/app/oracle/agent13c/agent_inst

Stop the agent

$AGENT_HOME/bin/emctl stop agent

Remove the old log files from AGENT_HOME/sysman/log

Delete any pending upload files from the agent home

rm -r $AGENT_HOME/sysman/emd/state/*

rm -r $AGENT_HOME/sysman/emd/upload/*

rm $AGENT_HOME/sysman/emd/lastupld.xml

rm $AGENT_HOME/sysman/emd/agntstmp.txt

rm $AGENT_HOME/sysman/emd/protocol.ini

Start the agent

$AGENT_HOME/bin/emctl start agent

Issue an agent clearstate from the agent home

$AGENT_HOME/bin/emctl clearstate agent

Force an upload to the OMS

$AGENT_HOME/bin/emctl upload agent

Finally I sometimes need to re-secure the agent

$AGENT_HOME/bin/emctl secure agent

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:

Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8

12.2 New Feature AFPASSWD utility to change password

Apps password change routine in Release 12.2 E-Business Suite changed a little bit. We have now extra options to change password, as well as some manual steps after changing the password using FNDCPASS.

There is a new utility introduced called AFPASSWD. This utility unlike FNDCPASS wont require you to enter apps and system user password, and makes it possible to separate duties between database administrator and application administrator. In most cases both these roles are done by same DBA. But in large organizations, there may be different teams that manage Database and Application.

Whether you use FNDCPASS or AFPASSWD to change the APPLSYS/APPS password, you must also perform some additional steps. This is because in R12.2, the old AOL/J connection pooling is replaced with Weblogic Connection Pool ( JDBC Data source ). Currently this procedure is not yet automated. It would be good, if this can be automated using some WLS scripting.

AFPASSWD Usage:
Changing SYSADMIN Password from application tier

AFPASSWD -f SYSADMIN
Enter the ORACLE password of Application Object Library ‘APPSUSER’:
Connected successfully to APPS.
Working…
Enter new password for user [SYSADMIN]:
Verify new password for user [SYSADMIN]:
Password is changed successfully for user SYSADMIN.
Password is changed successfully for user SYSADMIN.
AFPASSWD completed successfully.

FOR CHANGING APPLSYS PASSWORD WE NEED TO SHUTDOWN APPLICATION TIER AND ONCE WE FINISH CHANGING THE PASSWORD WE NEED TO RUN AUTOCONFIG ON ALL TIERS

Steps will be as below

1.SHUTDOWN APPLICATION TIER SERVICES
2.CHANGE PASSWORD
3.RUN AUTOCONFIG ON ALL TIERS
4.START APPLICATION TIER SERVICES.

How to change APPLSYS Password from Application Tier
AFPASSWD -c apps@EBSINSTANCE -s APPLSYS
Enter the ORACLE password of Application Object Library ‘APPSUSER’:
Connected successfully to APPS.
Enter the password for your ‘SYSTEM’ ORACLE schema:
Connected successfully to SYSTEM.
Working…
Enter new password for user:
Verify new password for user:
Working…
AFPASSWD completed successfully.

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:

How To Change The Password For The SYSADMIN User

we have 2 options:

We can use E-Business suite screens
We can use FNDPASS utility

Please follow below steps for can change sysadmin user password:

1. If we want to change sysadmin user password with E-Business suite

System Administrator -> User -> Query the desired USERNAME and in password tab enter the new password.

To test, relogin into the applications as the SYSADMIN user and the new password.
Verify that a concurrent program such as Active Users runs.

2. If we want to change sysadmin user password with FNDPASS utility

Keep all services running.
Login OS level by way of the applmgr user and source(run)n your environment scripts
cd $APPL_TOP
run APPSenvironment.env

cd $FND_TOP/bin
Run FNDCPASS to change the SYSADMIN password

FNDCPASS apps/apps 0 Y system/manager USER SYSADMIN <New Password>

Example:

FNDCPASS apps/apps 0 Y system/manager USER sysadmin/sysadmin123

Restart the Apache, Forms, Reports, 8.0.6 listener and concurrent manager services. << This step not mandatory, but recommended
To test, login to EBS as the SYSADMIN user with new password.
Verify that a concurrent program such as Active Users runs.

Reference:

How To Change The Password For The SYSADMIN User [ID 423274.1]

How to Change Applications R12 Passwords using Applications Schema Password Change Utility (FNDCPASS)? [ID 437260.1]

NEW FEATURE FOR CHANGING PASSWORD IN R12

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:

Restore a TDE Database backup file

At Destination Server:

Steps to Restore a TDE Database backup file of Source on Destination Server.

step 1) Create a new Master Key or Alter it using below if it already exists.
CREATE MASTER KEY ENCRYPTION BY PASSWORD=’OracleAgent@DBA$123′; — This can be from Source Server/New one.
–ALTER MASTER KEY ADD ENCRYPTION BY PASSWORD =’OracleAgent@DBA$123′

step 2) Restore the Master DB Certificate of Source Server on Destination Server:
USE master;
GO
CREATE CERTIFICATE TDE_Cert_New
fROM FILE = ‘D:\OracleAgent\TDE\TDE_Cert_New.cer’
WITH PRIVATE KEY(
FILE = ‘D:\OracleAgent\TDE\TDE_Cert_New_PrivateKey.pvk’,
DECRYPTION BY PASSWORD = ‘OracleAgent@DBA$123’
)

step 3) Finally Restore the TDE Enabled DB Backup File on Destination.

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:

Enable TDE on Source DB

• Create Master Key on MASTER DB
• Backup Master Key of Master DB
• Create Certificate on MASTER DB
• Backup Certificate on MASTER DB
• Create Encryption Key on User DB.
• Finally Enable TDE on User DB

At Source Server:
Step 1: Create Database Master Key on Master DB.
USE master;
GO
CREATE MASTER KEY ENCRYPTION BY PASSWORD=’OracleAgent@DBA$123′;
GO
–Use this if Master key already exists and to add a new Master Key.
–ALTER MASTER KEY ADD ENCRYPTION BY PASSWORD =’OracleAgent@DBA$123′;

Step-2: Backup Master Key of MASTER DB:
USE MASTER
BACKUP MASTER KEY
TO FILE = ‘D:\OracleAgent\TDE\MasterKey.key’
ENCRYPTION BY PASSWORD = ‘OracleAgent@DBA$123’

Step 3: Create a Certificate on Master DB to support TDE
USE master;
GO
CREATE CERTIFICATE TDE_Cert_New
WITH SUBJECT=’Database_Encryption’;
GO

Step-4: Backup Master DB Certificate & Private Key;
This step is not required to encrypt a database using TDE. But to make sure you can recover your encrypted data from a database backup, should your instance database become corrupted, or you want to move an encrypted database to another server, you should backup the certificate.
Run the following code:
USE master;
GO
BACKUP CERTIFICATE TDE_Cert_New
TO FILE = ‘D:\OracleAgent\TDE\TDE_Cert_New.cer’
WITH PRIVATE KEY(
FILE = ‘D:\OracleAgent\TDE\TDE_Cert_New_PrivateKey.pvk’,
ENCRYPTION BY PASSWORD = ‘OracleAgent@DBA$123’
)
Note: Store the PASSWORD in a safe place.

Step 5: Create Database Encryption Key on required User DB.
USE Advworks
GO
CREATE DATABASE ENCRYPTION KEY
WITH ALGORITHM = AES_256
ENCRYPTION BY SERVER CERTIFICATE TDE_Cert_New;

Step 6: Enable TDE on Database
ALTER DATABASE Advworks SET ENCRYPTION ON;

In below document i mentioned how to restore in destination server.

RESTORE TDE IN DESTIANTION SERVER

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:

How to find pending concurrent requests in 11i/R12

Below document describes how to find total pending concurrent requests in the system.

Some times our concurrent requests queue fill up. We find lot of requests in pending status. In that scenarios we need to find the total number of pending requests.

Please use below query to find pending concurrent requests details.

SELECT DECODE(phase_Code,’P’,’Pending’,’R’,’Running’)
phase
, meaning status
, count(*) numreqs
FROM apps.fnd_concurrent_requests, apps.fnd_lookups
WHERE LOOKUP_TYPE = ‘CP_STATUS_CODE’ AND lookup_code = status_code AND phase_code in ( ‘P’,’R’) and status_code!=’D’
and requested_Start_Date < sysdate
group by DECODE(phase_Code,’P’,’Pending’,’R’,’Running’) , meaning

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:

Troubleshooting RAC Load Balancer and FAN

Troubleshooting RAC Load Balancer and FAN :-

Below I mentioned simple steps:

Make sure tnsnames.ora has LOAD_BALANCE=ON
Server side Load Balance- Make sure remote_listener is set and pointing to correct entry in server side tnsnames.ora ( SCAN NAME – not the local listener)
If the desire is to get instance based LB make sure CLB_GOAL set to LONG and in cases set prefer_least_loaded_<listener_name>=OFF
If desire is to get LB on node load make sure CLB_GOAL is unset or set to NONE. Check prefer_least_loaded_<listener_name>=ON
If desire to get LB on service goodness then set CLB_GOAL=SHORT and also set Service Goal
Java application not receiving FAN events-check ONS, ICC
.NET and OCI application not receiving FAN events-check if aq_ha_notifications set for service, check system queue.
Java application not doing FCF-check if connection pool has FCF set/enabled
Check ONS, MMON, MMNL on server
Check PMON-enable trace, truss, strace, etc.
Oracle bugs

Notes:

REMOTE_LISTENER: A remote listener is a listener residing on one computer that redirects connections to a database instance on another computer. In a dedicated server RAC environment, we must enable the PMON background process to register with a remote listener. You do this by configuring the REMOTE_LISTENER parameter.

SCAN – Single Client Access Name This simply means client will just have the SCAN Name in the tnsnames.ora in the Client side and no need to know the Name of the nodes involved in the cluster to load balance . The SCAN Name is associated with one or more SCAN VIP’s (max of 3 VIP’s) . Client will get the SCAN Name and the request will be routed to the DNS and GNS and will get resolved by a single SCAN VIP which is associated to the SCAN Name . PMON will be frequently sending the load status on each node to the SCAN Listener and hence the SCAN listener will have a count on the load status on each node . Each Instance will be registered with the SCAN Listener and SCAN Listener will be aware of the load on each instance and will load balance the new requests accordingly .

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:

When SET DBID needed in RMAN?

Restrictions and Usage Notes for the SET DBID Command:

You should only run the SET DBID command in the following specialized circumstances:

You are not connected to a recovery catalog and want to restore the control file or server parameter file.
You are connected to a recovery catalog and want to restore the control file, but the database name is not unique in the recovery catalog.

When you restore the control file, you must use the SET DBID command to identify the target database. The DBID is used to determine the location of control file auto backups.

We can get the DBID from below query

when we run the rman to connect the target database:

If you are using RMAN catalog, and you have a clone of your database with the same DBID, how the RMAN will differentiate between them?. Here you need to change the DBID of the cloned database using DBNEWID utility to avoid confusion.

In this below blog i showed you how to change DATABASE Name with DBNEWID utility.

Change DB name with DBNEWID Utility in 19c

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:

SCP between two cloud instances

In this article we are going to see how to transfer the files from one cloud instance to another using scp.(server copy)

Step:1 Trying to copy from Chennai server to Chennai-clone server.

Below errors will come,

Follow the below steps to resolve this error,

Step:2 We need to create the ppk of Chennai-clone server without extension as mentioned here.

Open puttygen
Click conversions
Click Import key
Load the ppk file (i.e) Chennaiclone.ppk
Click conversions
Click Export OpenSSH key
Save the file without extension
Move the saved file to the Chennai server

Step:3 After that try to send the files using scp from one instance to another.it works fine and I have successfully transferred the files.

scp -i chennaiclone *.bkp [email protected]:/home/opc

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:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8

Oracle Zero Downtime Migration 21c

Zero Downtime Migration (ZDM) 21c is available for download! ZDM is Oracle’s premier solution for moving your on-premises Oracle Database workloads to Oracle Cloud, supporting a variety of Oracle Database versions as the source and most Oracle Cloud Database Services as targets. Zero Downtime Migration 21c enhances the existing functionality by adding the long-requested Logical Migration workflow, which provides even more zero downtime migration choices!

For more reference: blogs.oracle.com click the below link

Oracle Zero Downtime Migration 21c

Logical Migration

In addition to the Physical Migration workflow which has been supported since the first version of ZDM (see for example: https://blogs.oracle.com/maa/announcing-oracle-zero-downtime-migration-release-197), ZDM 21c offers a Logical Migration to the Oracle Cloud in eight simple steps, which can be scheduled and monitored as needed. The Logical Migration workflow allows you to migrate to Oracle Autonomous Database leveraging ZDM automation.

You can leverage two logical migration workflows with different methodologies:

Logical Offline Migration
- Data Pump and Database Links based methodology
- Data Pump and Backup Location based methodology
Logical Online Migration
- GoldenGate, Data Pump and Database Links based methodology
- GoldenGate, Data Pump and Backup Location based methodology

Exadata On-Premises Support

Oracle ZDM 21c includes Exadata Database Machine as a new target. You can now migrate your current database deployments to an on-premises Exadata Database Machine, leveraging the full automation and power of ZDM. Migration to Exadata On-Premises is only supported via ZDM’s physical migration workflow.

Autonomous Database Support

Oracle ZDM 21c can now migrate databases directly to Autonomous Database using any of the logical migration workflows. Supported targets are:

Autonomous Transaction Processing (Shared & Dedicated)
Autonomous Data Warehouse (Shared & Dedicated)
Autonomous Database on Exadata Cloud at Customer

Non-CDB to CDB Migration Support

Non-CDB to CDB Migration is now supported in both Oracle ZDM’s physical and logical migration workflows, providing you with more migration flexibility via a simplified migration process that includes the Non-CDB to PDB conversion and hence, a wider choice of cloud targets.

Pre-Migration Advisor

A pre-migration advisor that evaluates the source database for feature compatibility and other limits is now included in the logical migration workflow only. You should leverage this advisor in order to better prepare for your database migration journey.

Support for Database Links

Logical Database Migration offers the possibility to establish direct Database Links between the source and the target, thus avoiding the need for a backup location as part of the migration workflow. Support for Database Links is optional, as you can also leverage a backup location such as Object Storage, NFS or the Recovery Appliance for your migration. Database Links based migration is not supported for Autonomous Database Dedicated.

Lighter ZDM Home

The Oracle ZDM software home is now lighter and more compact. Users will notice the difference already when downloading the binaries. ZDM installation and deployment has also been optimized and trimmed, allowing for an even faster instantiation of your first migration.

Tag Archives: oracle 19c

Steps to Restore a TDE Database backup file of Source on Destination Server.

Enable TDE on Source DB

How to find pending concurrent requests in 11i/R12

Restrictions and Usage Notes for the SET DBID Command:

Logical Migration

Exadata On-Premises Support

Autonomous Database Support

Non-CDB to CDB Migration Support

Pre-Migration Advisor

Support for Database Links

Lighter ZDM Home