May, 2018 - alfredokriegdba.com

How To Connect To The Oracle Cloud DB Instance?

In my previous post (How To Create An Oracle Cloud Instance) I showed you create your first Oracle Cloud DB instance. Now that the instance is there the question is, how to connect to it?

Let’s say you want to connect using SQL Developer to start creating objects and inserting data. First you need to enable the Client Access feature. Yes, it is disabled by default.

Navigate to the Cloud DB instance dashboard. Click on Manage menu on the left side.
Click on Admin Password and provide a password for the PDB_ADMIN account.

Then click on Client Access and check the enabled flag, then save.

It will show like this.

Once this is enabled you need to download the Access Credentials in order to connect to your instance.

Click on the Client Credentials button located on the right side of the Client Access one. This is going to prompt for a password (type one that you can remember) and it will download a .zip file containing these credentials and connect descriptors.

Note: You don’t have to unzip this file.

Open your SQL Developer software and click on New Connection.

Type a name for your connection. In the username & password you can either type the PDB_ADMIN username and password or the credentials for the newly created schema.

In Connection Type select Cloud PDB and provide the downloaded .zip file along with the password provided (the one that you should remember).

It should look like this.

Click Save and then Connect.

Now let’s test our connection by executing a simple SQL statement.

Using the Cloud DB instance dashboard you can create different schemas as needed.
You just provide the username and password.

At the end you just need to follow the same steps as we did before, just provide the username and password of the new schema.

More information can be found at:

https://docs.oracle.com/en/cloud/paas/exadata-express-cloud/csdbp/connecting-sql-developer.html#GUID-238A40BD-10E9-4478-AAA3-43FC98519D3F

Thanks,
Alfredo

How To Create An Oracle Cloud Instance

In my previous post (Thinking on trying the Oracle Cloud? My 30 day experience) I showed you how to subscribe to the Oracle Cloud and how to get to the main dashboard. From here we are going to click on the Create Instance button.

After that you are going to be prompted on what kind if service this instance is for. You have 4 options; Messaging, Data Visualization, Exadata Express and Management Cloud.

In this example we want to create a database instance on Exadata Express. So we are going to select “Create” on the Exadata Express section.

Then you need to configure the instance details. First is the name (lowercase), then the plan and finally the Database shape. In this case I just want to create a small 20GB test instance.

On the right side you have administrator details. The default is the account we created to sign up to the Oracle Cloud.

Then click on Create.

You will get a message like the one below.

It took couple of minutes for the DB instance to be provisioned. Once ready, you’ll see the status of the instance as active in the dashboard.

Next click on the service instance URL and you will be re-directioned to the instance dashboard. In this dashboard you have 2 main options, Develop and Manage.

Develop option, gives you tools like SQLPlus, App Builder, SQL Developer and the option to enable access to client tools.

Manage option enables you to create users, change passwords, export/import and Apex administration.

This concludes the instance creation process.

Thanks,

Alfredo

Thinking on trying the Oracle Cloud? My 30 day experience.

Although I already had some exposure to the Oracle Cloud (thanks to other Oracle ACEs that put an awesome workshop last year at Collaborate 2017) , I decided to sign up for a free 30 day ($300 dollars credit) and test the Cloud out.

The sing up process was kind of weird. You first go to https://cloud.oracle.com/home and click on the “Try for Free” green button in the right upper corner and then “Create Free Account”.

Then you fill the formulary with all your personal data (account details), verification code (sent to your cell), credit card details (no charge will be made) and you need to agree the terms and conditions.

You will receive an email after you submit your formulary. That night I received an email from Oracle that asked me to provide the name of the bank of my credit card and the amount that was charged to it. Yes, they charged and then they removed the charge.

After asking them by email on how to provide this information, they responded that just by replying to that email with my information (seems pretty secure, right?). I received an email couple of hours later with my login credentials and the URL. Once you click on the hyperlink or type the URL provided, you are prompted to reset your password and then sent to the main dashboard.

In my next post, I will show you how to create your first Cloud Database instance.

Thanks,

Alfredo

ORA-04045 When Running ADOP PHASE=ACTUALIZE_ALL




Oracle’s documentation recommends to execute actualize_all in
order to purge old editions in the DB accumulated during previous patching
cycles.




There’s a problem with EBS version 12.2.4 that when running adop
phase=actualize_all you get an ORA-04045 errors during
recompilation/revalidation of .




You can try to manually recompile objects but all of them fail
with the same error. This is documented under bug 24489846.




Follow the instructions on the MOS note id 2187877.1.




I also recommend to open an SR as this bug is still open as of
May 2018.




Thanks,

Alfredo

TXK patch failing with ORA-600

I got an error during an TXK patch in a 12.2 EBS instance.

This happened while executing file xdotmgen.ldt.

Error: FAILED: file xdotmgen.ldt on worker 1 for product fnd username APPS.

Uploading from the data file

….

Uploading from staging tables Error during uploading. ORA-00600: internal error code, arguments: [17273], [0x13C88677A0], [0], [7], [], [], [], [], [], [], [], []

After looking at MOS Note Id 1953472.1, it turns out to be due to a couple of invalid objects in the database.

The solution worked and were able to continue with the ADOP cycle.

ALTER PACKAGE APPS.FND_EXECUTABLES_PKG COMPILE BODY;

ALTER PACKAGE APPS.FND_SEED_STAGE_UTIL COMPILE BODY;

Thanks,

Alfredo

OEM 12c Agent Crashing on Solaris

I recently had an issue with an OEM agent 12.1.0.4 version running on Solaris. Looks like there’s a Java related bug which causes the agent to consume high amounts of CPU in the box. But the interesting part is this only happens when Listeners are being monitored. If you blackout the Listener targets this stops.

If this’s the case then you are hitting Bug 15953286.

The solution is comprised by various steps outlined on MOS “EM 12c: Enterprise Manager 12c Cloud Control Agent CPU Spiking and High Utilization on Solaris with Many Database and Listener Targets (Doc ID 1536871.1)”.

Thanks,

Alfredo

OEM 13c – Unable to find agent in a patch plan

If you have an issue to find an agent using a patch plan from OEM 13c, then you are likely facing a bug.

Oracle explains the rationale in the MOS Id 2240307.1.

You need to apply patch 25604219 in order to fix this issue. After this you can search your agent and add it to the patch plan.

Thanks,

Alfredo

OEM 13c and Amazon’s RDS

Amazon released a note late last year about Amazon’s RDS is now supporting Oracle Enterprise Manager Agents.

Amazon RDS supports agent version 12 (12.1.0.5), 13R1 and 13R2 (13.2.0.0).

You can use this to monitor your DB instances running on Amazon’s RDB but there are some limitations, like the fact you cannot execute jobs against those targets.

See below for more information about this.

https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Oracle.Options.OEMAgent.html

Thanks,

Alfredo

OEM 13C Useful EMCTL Agent Commands

Here’s a list of some useful emctl commands to manage your OEM 13c agent.

Get the status of the agent:

$ emctl status agent

Oracle Enterprise Manager Cloud Control 13c Release 2

—————————————————————

Agent Version : 13.2.0.0.0

OMS Version : 13.2.0.0.0

Protocol Version : 12.1.0.1.0

…

Last Reload : (none)

Last successful upload : 2018-05-15 09:04:32

Last attempted upload : 2018-05-18 13:12:29

Total Megabytes of XML files uploaded so far : 13.6

Number of XML files pending upload : 1,956

Size of XML files pending upload(MB) : 3.64

Available disk space on upload filesystem : 81.90%

Collection Status : Collections enabled

Heartbeat Status : OMS is unreachable [not running]

Last attempted heartbeat to OMS : 2018-05-18 13:12:02

Last successful heartbeat to OMS : 2018-05-15 09:10:00

Next scheduled heartbeat to OMS : 2018-05-18 13:12:44

—————————————————————

Agent is Running and Ready

Get the list of targets currently monitored by the agent:

$ emctl config agent listtargets

Oracle Enterprise Manager Cloud Control 13c Release 2

[localhost.localdomain.com, host]

[localhost.localdomain.com:3872, oracle_emd]

[Management Services and Repository, oracle_emrep]

…

[/EMGC_GCDomain/GCDomain/EMGC_OMS1, weblogic_j2eeserver]

[NodeManager_localhost.localdomain.com_1, weblogic_nodemanager]

[oms13c1_1_localhost.localdomain.com_4754, oracle_home]

Get the status of a particular target:

$ emctl status agent target /EMGC_GCDomain/GCDomain/EMGC_OMS1,weblogic_j2eeserver

Oracle Enterprise Manager Cloud Control 13c Release 2

—————————————————————

Target Name : /EMGC_GCDomain/GCDomain/EMGC_OMS1

Target Type : weblogic_j2eeserver

Current severity state

———————-

Metric Column name Key State Timestamp

——————————————————————————–

Response Status n/a CRITICAL Fri May 18 13:13:25 EDT 2018

alertLogAdrIncident adr_problemKey Fri Jun 23 16:07:21 2017/254 CRITICAL Fri Jun 23 16:07:58 EDT 2017

alertLogAdrIncident adr_problemKey Fri Jun 23 16:08:10 2017/263 CRITICAL Fri Jun 23 16:12:58 EDT 2017

alertLogAdrIncident adr_problemKey Mon Jul 10 06:06:34 2017/290 CRITICAL Mon Jul 10 06:08:52 EDT 2017

alertLogAdrIncident adr_problemKey Mon Jun 26 13:04:51 2017/272 CRITICAL Mon Jun 26 13:08:48 EDT 2017

alertLogAdrIncident adr_problemKey Tue Jun 27 17:50:54 2017/281 CRITICAL Tue Jun 27 17:53:48 EDT 2017

jvm heapUsedPercentage.value n/a CLEAR Tue May 15 09:07:27 EDT 2018

jvm_threads deadlockedThreadCount.value n/a CLEAR Tue May 15 09:06:15 EDT 2018

—————————————————————

Agent is Running and Ready

Clear the current status of a target’s metrics:

$ emctl clearstate agent /EMGC_GCDomain/GCDomain/EMGC_OMS1,weblogic_j2eeserver

Oracle Enterprise Manager Cloud Control 13c Release 2

Clear target severity state

Now they show as undefined until the next collection happens:

$ emctl status agent target /EMGC_GCDomain/GCDomain/EMGC_OMS1,weblogic_j2eeserver

Oracle Enterprise Manager Cloud Control 13c Release 2

—————————————————————

Target Name : /EMGC_GCDomain/GCDomain/EMGC_OMS1

Target Type : weblogic_j2eeserver

Current severity state

———————-

Metric Column name Key State Timestamp

——————————————————————————–

Response Status n/a UNDEFINED Fri May 18 13:14:25 EDT 2018

alertLogAdrIncident adr_problemKey Fri Jun 23 16:07:21 2017/254 UNDEFINED Fri Jun 23 16:07:58 EDT 2017

alertLogAdrIncident adr_problemKey Fri Jun 23 16:08:10 2017/263 UNDEFINED Fri Jun 23 16:12:58 EDT 2017

alertLogAdrIncident adr_problemKey Mon Jul 10 06:06:34 2017/290 UNDEFINED Mon Jul 10 06:08:52 EDT 2017

alertLogAdrIncident adr_problemKey Mon Jun 26 13:04:51 2017/272 UNDEFINED Mon Jun 26 13:08:48 EDT 2017

alertLogAdrIncident adr_problemKey Tue Jun 27 17:50:54 2017/281 UNDEFINED Tue Jun 27 17:53:48 EDT 2017

jvm heapUsedPercentage.value n/a UNDEFINED Tue May 15 09:07:27 EDT 2018

jvm_threads deadlockedThreadCount.value n/a UNDEFINED Tue May 15 09:06:15 EDT 2018

—————————————————————

Agent is Running and Ready

Force the agent to collect dynamic properties:

$ emctl reload agent dynamicproperties /EMGC_GCDomain/GCDomain/EMGC_OMS1:weblogic_j2eeserver

Oracle Enterprise Manager Cloud Control 13c Release 2

—————————————————————

EMD recompute dynprops completed successfully

Thanks,

Alfredo

Oracle EBS 12.2 EBS Technology Codelevel Checker ETCC

Looks like this is my first post about Oracle EBS. Yeah, looks like now I’m more on the dark side of the force.

This is the time for ETCC. ETCC is a set of 2 scripts. One is going to check the recommended patches for the DB stack and the other one is going to check for the recommended patches for the Middleware stack.

It does not connect to the internet to verify the latest patches. So you must verify and download the latest version of this (patch 17537119).

The scripts are:

– checkDBpatch.sh

– checkMTpatch.sh

You just execute these scripts and provide the information that is being asked. They are going to spool a report like list with the recommended patches for your stack.

Keep in mind that they make use of utilities like OPatch, so is recommended you have the latest version in your DB Oracle Home.

Identifying database release.

Database release set to 12.1.0.2.

Connecting to database.

Database connection successful.

Checking for DB-ETCC results table.

Table to store DB-ETCC results already exists in the database.

Checking if InMemory option is enabled.

Obtained list of bugfixes to be applied and the list to be rolled back.

Now checking Database ORACLE_HOME.

The opatch utility is at the required version.

Found patch records in the inventory.

Missing Bugfix: 11111111 -> Patch 12345678

Missing Bugfix: 22222222 -> Patch 45678912

Missing Bugfix: 33333333 -> Patch 98765432

Missing Bugfix: 44444444 -> Patch 98765432

Generating Patch Recommendation Summary.

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

PATCH RECOMMENDATION SUMMARY

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

The default patch recommendations to install these missing bugfixes are:

——————————————————————————–

Oracle Database Release 12.1.0.2 (No PSU applied)

——————————————————————————–

Patch 12345678

– Filename: p12345678_121020_Linux-x86-64.zip

Patch 45678912

– Filename: p45678912_121020_Generic.zip

Patch 98765432

– Filename: p98765432_121020_Linux-x86-64.zip

Apply the required patches and rerun this script.

As a side note, I noticed that with TXK Delta 10 if you try to start an ADOP cycle it is going to check if ETCC was recently executed and all the recommended patches are in place.

Looks like is some way to enforce that all the tech stack patches are current.

Thanks,

Alfredo