Using Oracle SQL Developer to Connect to Microsoft SQL Server
A client likes to use Oracle SQL Developer to connect to Microsoft SQL server. During the configurations, some errors occurred. This post shows how to resolve the configuration issues from Oracle SQL Developer and third party libraries .
Read more of this content when you subscribe today.
As per Oracle doc, upgraded OEM 12c agents to 13c with following steps:
To upgrade agents via OEM console->Manage Cloud Control ->Upgrade agents -> Agent Upgrade tasks-> ……
To clean up old agents home after upgrading via OEM console ->Manage Cloud Control -> Upgrade agents -> Post Agent Upgrade tasks -> ……
After Oracle Enterprise Manager Agents have been upgraded from 12c to 13c, the new agent binary is still under old agent base directory like “/u01/app/oracle/product/agent12g/agent_13.2.0.0.0″.
For having a meaningful naming and future convenience, I’d like to relocate the agent base directory from “/u01/app/oracle/product/agent12g” to “/u01/app/oracle/product/agent” with following steps:
Read more of this content when you subscribe today.
While installing Oracle Database 11.2.0.4 RAC in 19c GI, the following errors occur:
INFO: Verification Result for Node:racnode1 WARNING: Result values are not available for this verification task INFO: Error Message:PRVF-4037 : CRS is not installed on any of the nodes INFO: Cause: Could not identify a CRS installation on any node. INFO: Action: Ensure that CRS is installed on all the nodes participating in the operation. INFO: *** INFO: Node Application Existence: This test checks the existence of Node Applications on the system. INFO: Severity:CRITICAL INFO: OverallStatus:OPERATION_FAILED INFO: -----------------------------------------------
Read more of this content when you subscribe today.
Then rerun the installation successfully.
[oracle@racnode1 ~]$ /tmp/database/runInstaller -silent -responseFile /home/oracle/11204_install_rac.rsp -showProgress ... .. . ………………………………………….. 9% Done. Prepare successful. Copy files in progress. ………………………………………….. 15% Done. ………………………………………….. 20% Done. ………………………………………….. 25% Done. ………………………………………….. 30% Done. ………………………………………….. 36% Done. ………………………………………….. 41% Done. ………………………………………….. 46% Done. ………………………………………….. 51% Done. ………………………………………….. 56% Done. Copy files successful. ………. Link binaries in progress. Link binaries successful. ………………………………………….. 77% Done. Setup files in progress. ………………………………………….. 94% Done. Setup files successful.
In your environment, there are hundreds or even thousands of targets managed by OEM, and a doze or even hundreds of OEM administrators and users. In this case, effectively and securely managing Named Credentials ( NC ) is a challenging job. Usually, every OEM administrator or user creates and manages their own Named Credentials ( NC ). So many duplicate copies of Named Credentials ( NC ) are kept, it brings difficulties for updating them if any targets credentials changed.
This post demonstrates how to share a Named Credentials ( NC ) with many administrators and users in any size of OEM environment by using a role. Same as an Oracle database role, which can be granted to a role or a user.
The following content is only available to subscribers only.
It makes DBA life easy by using new feature of Data Guard Standby Automatic Password file Synchronization
For 12cR1 and earlier versions, when setup DataGuard( DG), if there is a change in password file of Primary database , then the password file needs to be copied from Primary database to standby database server. Otherwise the DG will get errors.
Read more of this content when you subscribe today.
Make DBA Life Easy 