Connect OCI DB system using Console Connection

 


 

Step 1:

In your local machine, open terminal (Windows Powershell) and generate key pair

PS C:\Users\admin> ssh-keygen -t rsa

Generating public/private rsa key pair.

Enter file in which to save the key (C:\Users\admin/.ssh/id_rsa):

Enter passphrase (empty for no passphrase):

Enter same passphrase again:

Your identification has been saved in C:\Users\admin/.ssh/id_rsa

Your public key has been saved in C:\Users\admin/.ssh/id_rsa.pub

The key fingerprint is:

SHA256:5Ioqw+KE2SJqgucRgjxXNhCpzZOBMgH4zSl/vYpD1Ec arunkumar k@doyenltp1980

The key's randomart image is:

+---[RSA 3072]----+

|=..oo            |

|+. o.   E        |

|.o+oo* ..        |

|o.o=B oo.        |

|oo.=.  oS        |

|.+o.o....        |

|B.o....  .       |

|X+.o..  .        |

|**o ....         |

+----[SHA256]-----+

PS C:\Users\admin>

 

Step 2:

Copy the contents of public key

PS C:\Users\admin> cat C:\Users\admin/.ssh/id_rsa.pub

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDKYsAVXzjj1dmLevNjKdJkK7so6efkrlLq7Iy9jVOLcvsEOR4lFprAyXq+sQIl+xSzdlcEl7mFrbf+dzb2gzewWiGn6cj5zPRgQ6CVElhHizFFEfv9Nn2X4p3heeligRwnj4Alw80iqEaC3vf4a9b8npkQ05t0cRHJzX/Go/+NhLkwBA7XvfnrUY9iry05wLl1dzj+BseD3JuK/Zj8dx9mhCCurTh1bc72k1DMDSzlfpHifuFBLXylNPmEe/o3orHppakhbki7dYZTNuqS9jdXvZyWnA1oNYslCS773yULfFi82Dbdhpbp71B10jgKVt1t/AdoMLc7iT4UEDFUTcmIbNDp1raqtGb1LPgOl1G9WQhYzSLV3ciDtcMAYRTKmjljDkm/W9FMCZ2qZO3CCDkB4JchhLyhSzN51c+4a7nWG+xhXpI68wRJ5Q0xkpVmc84S6RUiybgLpyxblWgH5qAoHQm5OFiP89IqmcJt/U//VbavslvDlAzHUWM5tXhYb8E= username@desktop

PS C:\Users\admin>

Step 3:

 

Database service -> select the Database system -> consoleconnections-> click “Create console connection”

 

 

 

Step 4:

 

Add the public key you copied from step 2:

 

Step 5:

Once it is available after the below creating stage

 

A screenshot of a computer AI-generated content may be incorrect.

Copy the ssh string and paste in notepad.

 

A screenshot of a computer AI-generated content may be incorrect.

Step 6:

 

Switch to you local desktop and cd to .ssh directory.

A computer screen with white text AI-generated content may be incorrect.

 

Step 7:

Paste the SSH string and press enter and you will see the prompt asking for login.

 

ssh -o "HostKeyAlgorithms=+ssh-rsa" -o "PubkeyAcceptedAlgorithms=+ssh-rsa" -o ProxyCommand='ssh -W %h:%p -p 443 ocid1.instanceconsoleconnection.oc1.phx.anyhqljtwdx4egacfcdgmnzwb4itm3i3utnvuuwopeczdoyu6akmxgqev7aa@instance-console.us-phoenix-1.oci.oraclecloud.com' ocid1.instance.oc1.phx.anyhqljtwdx4egacejrj33wgjwhpcmn3xzafpv2htje66pa3ngtu5niy2wiq

 

A black screen with white text AI-generated content may be incorrect.

 

Step 8:

Go back to OCI console and reboot the node and come back to you local machine and press enter. You will see the below message. As soon as you see this message, press up or down key to pause the reboot.

A screenshot of a computer error AI-generated content may be incorrect.

 

Step 9:

As soon as you see reboot message, press up or down key to pause the reboot. You will end up with below screen.

 

A screenshot of a computer AI-generated content may be incorrect.

 

Step 10:

You may proceed with your troubleshooting.

 

 

 

 

 

at No comments:

Understanding Data Types in Oracle E-Business Suite

Oracle E-Business Suite (EBS) contains a wide range of data categories, each serving different purposes within the system. Recognizing these types helps in managing, optimizing, and archiving your data effectively.

1. Transient Data

This data is short-lived and typically used for intermediate processing. It includes:

  • Interface tables

  • Temporary tables

  • Working storage used during concurrent processing

2. System Audit and Diagnostic Data

Used primarily for monitoring and auditing purposes, this data supports:

  • User login tracking

  • Concurrent request history

  • Diagnostic logs for performance and troubleshooting

3. Transactional Data

This includes both fiscal and non-fiscal operational data, such as:

  • Invoices, orders, and payments

  • Workflow activities and logs supporting transaction processing

Transactional data tends to represent the highest volume in most EBS environments and is a common target for purging and archiving.

4. Master and Setup Data

This is critical reference and configuration data that drives transaction processing:

  • Suppliers, addresses, inventory items

  • Lookup codes and setup metadata configured by customers

While it can grow large in some instances, Master and Setup data is rarely purged and is typically smaller in size compared to transactional data.

5. Seed Data

Seed data is pre-populated during the initial installation of Oracle EBS and includes:

  • Default configuration

  • Lookup values

  • Standard setup definitions

📌 Data Volume Insights

  • Transactional data typically dominates in volume and is a primary candidate for performance tuning, archiving, or purging strategies.

  • Transient and audit data follow closely in volume and retention sensitivity.

  • Master, Setup, and Seed data, while essential, are generally more static and less suited for bulk deletion.

Understanding these classifications enables better data lifecycle management, performance tuning, and compliance planning in Oracle E-Business Suite environments.

at No comments:

Beginner’s Guide to ORA-600/ORA-7445/ORA-700 Look-up Tool


If you've ever come across strange errors like ORA-600, ORA-7445, or ORA-700 while working with Oracle databases, you’re not alone. These internal errors can seem cryptic, especially if you’re new to Oracle support. Thankfully, Oracle provides a Look-up Tool to help decode these errors and guide you toward a solution.

In this post, we’ll walk you through how to use this tool in a few simple steps.

🔧 What Is the ORA-600/ORA-7445/ORA-700 Look-up Tool?

The tool helps identify known issues related to internal Oracle errors. These errors often look like:

ORA-600 [argument1]  
ORA-7445 [argument1]  
ORA-700

These aren't typical user errors, but rather indicators of low-level internal problems in the Oracle kernel. The Look-up Tool compares your error against Oracle's internal database of bugs and known issues.

📝 Steps to Use the Look-up Tool

1. Install Oracle Trace File Analyzer (TFA)

Make sure you have the latest version of Oracle TFA installed. This tool helps you collect diagnostic data automatically.

👉 Download it here: Oracle Trace File Analyzer (TFA)

2. Collect Diagnostics Automatically

Use TFA to collect the logs by running one of the following commands based on your error type:

tfactl diagcollect -srdc ORA-00600
tfactl diagcollect -srdc ORA-07445
tfactl diagcollect -srdc ORA-00700

This will gather all necessary logs and trace files.

3. Upload to the Troubleshooting Tool

Upload the zip file generated to either of the following:

The tool will scan the logs and suggest known causes, bugs, and possible solutions.

4. Still Need Help?

If the tool doesn’t return a useful result, attach the diagnostic zip file and raise a new SR (Service Request) with Oracle Support. You can do this from the troubleshooting tool page itself by clicking Create SR at the bottom.

🛠️ Bonus Tip: Use interpret Tool in dbse

If you have access to Oracle’s internal tools (like in MOS ISDE), you can use the interpret command:

interpret -format=text error "ORA-600 [3020][1][2][3]"

This can help decode the arguments and point to the root cause.

✅ Summary

The ORA-600/7445/700 Look-up Tool simplifies the first step of troubleshooting complex Oracle internal errors. Here's what to remember:

  • Always collect diagnostics using TFA.

  • Use the right diagcollect command for your error type.

  • Upload the file to Oracle’s troubleshooting portal.

  • Raise an SR if no known issue matches.

Next time you hit one of these scary-looking errors, don’t panic—just look it up! 💡

Let me know if you'd like this formatted for LinkedIn or internal knowledge base publishing.

at No comments:
Subscribe to: Posts (Atom)