Failure -Test failed: ORA-00257: archive error. Connect internal only, until freed

Check the status of the archive log

Check the database archive log destination

It is showing archive log space is full

Remove some archive log files

If we get limit exceed error, increase the archive log size as below

ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE=20048576000 SCOPE=BOTH;

Restart the database

How to kill forcefully running oracle database process in linux

Connect to server through putty and issue the below command

ps -ef |grep pmon

Now kill the port running the process ora_pmon_orcl as below

Command to get the patch set applied on oracle database

select * from sys.registry$history;

Steps for preventing Oracle SQL Developer sessions from being killed

In general when we leave the database connection opened for a while in oracle sql developer, It will throw a "connection timeout" message when we tried to run a query next time.
We have to reconnect the connection for running the query.

To keep the database connection alive in sql developer please follow the below steps:

For Oracle SQL Developer 3 Versions:

1. Download oracle.sqldeveloper.keepalive.jar from this link " https://454e35d1-a-62cb3a1a-s-sites.googlegroups.com/site/keepaliveext/oracle.sqldeveloper.keepalive.jar?attachauth=ANoY7cp8U9ULxrRvTu3b-96lNNGvQAyh_LQ_kRfPmskJS0-qDvLfvoEeyd1jVFkbTRsso4wMuH65pMFVrXECLpUsFXj7D9wxGbYZrBffFy6FNAVRpCVy-j5vJ9h84DdMl_tCBGHaI3_GJzjx2OwutMk2b-bdCvOV_lgSy7_Kb3J2T2CjCR9hg9o_Bk_3f5roc86Vr6XxkncVkpZ87XsphHtEmZveLTVzdHcqf1_a9QEKY77koOcbkKU%3D&attredirects=0"

2. Copy the downloaded jar file to the below location

%SQLDEVELOPER_HOME%\sqldeveloper\extensions

3. Open sql developer and right click on a connection and go to Keep-Alive and select Active

4. Enter the user and password details of the connection if it is not already connected

5. We will get a success keep alive message

6. Now check again for the session time out issue.

For Oracle SQL Developer 4 Versions:

1. Navigate to %SQLDEVELOPER_HOME%\sqldeveloper\bin

2. Open sqldeveloper.conf file

3. Add " AddVMOption -Doracle.net.disableOob=true" to the file and save it.

4. Open sqldeveloper-nondebug.conf file

5. Add " AddVMOption -Doracle.net.disableOob=true" to the file and save it.

6. Open sql developer and connect to the database and check for session time out

OWB repository seeding failed

When we are working with owb repository assistant for the first time we may get the below error

To resolve this :

1. Connect to the database as sysdba user and run the remote_owb_install.sql and provide the OWB_REMOTE_ADMIN directory as below

2. Execute the OWB scripting command to seed the repository

Navigate to $ORACLE_HOME/owb/bin/unix and open the shell ombplus by running the command OMBPlus.sh as below





Execute the below command to seed the OWB repository





3. Now relaunch the repository assistant and try to create workspace

Resolution : ORA-01157: cannot identify/lock data file 6 - see DBWR trace file

When we are working with oracle database some times the database may not open with the below errors:

ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
ORA-01110: data file 6: 'C:\APP\ADMINISTRATOR\ORADATA\ORCL\DEV_SVCTBL.DBF'

Solution:

To resolve this error issue the below sql commands and try to open the database

1. select name from v$datafile where file#=6;
2. alter database datafile 6 OFFLINE DROP;
3.alter database open;

When we try to open the database again we may get data file error

Repeat this step until all the error data files got dropped
Ones this got resolved we can open the database

Steps for creating oracle workflow manager owb 11g

Run the below command to install oracle workflow manager

Provide the details and click on submit

Click ok after successful installation

starting and stopping repository browser owb

To start the Warehouse Builder Browser Listener:

The first time you invoke this listener, select and re-confirm a password for an oc4jadmin account

Open the repository browser to check with the below url

https://localhost:8999/owbb/RABLogin.uix?

Give the login details and select design center to login to owb design center

Select control center to login to owb control center

To stop the Warehouse Builder Browser Listener:

Steps for Launching Designer Center OWB

Launching Designer Center

Provide the details and click ok

Configuring repository for OWB 11G in oracle database 12C

Checking for java virtual machine in database

Checking for java objects

Checking for java roles

Running the scripts

Clean_owbsys.sql 

The clean_owbsys.sql script drops the contents of any existing OWBSYS schema installations, but leaves the schema otherwise intact.

Before proceeding you will have to default tablespace for  temp:

cat_owb.sql

The cat_owb.sql script checks if an OWBSYS schema exists, and creates it if necessary, and then installs the objects required by OWB 11.2 repository.

Unlock the users with the below scripts

reset_owbcc_home.sql

The reset_owbcc_home.sql script ensures that Oracle Warehouse Builder uses the 11.2 version of the Control Center Service

Granting remote server installation

Creating repository workspace

Run the repository assistant as below

Click next in the welcome screen

Give the database details and click next

Select manage warehouse builder workspace and click next

Select create new warehouse builder workspace and click next

Select create a workspace as new user a workspace owner and click next

Give database username and password and click next

Select the features we want and click next

Provide the details and click next

Provide owbsys user information and click next

Select any existing user or create new user for workspace and click next

In the repository summary screen click finish