ORA-17627: ORA-01017: during standby creation with RMAN

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/17/2011 07:38:34
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on p1 channel at 11/17/2011 07:38:34
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-01017: invalid username/password; logon denied
ORA-17629: Cannot connect to the remote database server

We need to see first the script we execute to create the standby.

As this is 11g, we have a feature that we can make a standby database using rman duplicate db, even when the backup of primary database is not available.

So to use that feature executed below RMAN commands on target server.

rman target / auxiliary sys/pass@STANDB

run
{
allocate channel p1 type disk;
allocate auxiliary channel sb1 type disk;
duplicate target database for standby from active database;
}

And this ended up with above error.

Two things to be checked in this case:

1. Simply try logging in to each of the database using service name from the other server.(remote login)
from standby - sqlplus sys/passs@PRIME
from primary - sqlplus sys/passs@STANDB

2. For executing this we have to connect both the databases using service name and if the target is connected as / then above error occurs.

Another error message will appear if we connect standby as /, but that states clearly to connect auxiliary database using service name.

So the right way of connecting using service name is

rman target sys/passs@PRIME auxiliary sys/pass@STANDB

Weblogic Console : another user already owns the lock

Sometimes on Weblogic Console we see below message

"another user already owns the lock"

To come out of such a situation you need the user who has made the changes or if you have an admin user, you can take the lock.

Table Fragmentation

The delete from the table deletes the rows but doesn't frees up the memory neither changes the high water mark.

The best way to get the memory cleared is truncating the table, but this hardly gets done in practical systems, and most of the time the delete and insert operations takes place.

So due to delete operations table gets fragmented, and in simple words its size appears more then the actual size of data it has. ( This will appear only if the compression is not enabled, check compression in dba_tables against the table).

Below query can help in identifying the tables which has different tablesize and actualsize, order by the maximum of difference.

Data Guard - 1 ( Physical Standby )

Standby databases may be set up in two ways.

1. Physical

2. Logical

The characteristics and pros n cons can be discussed in parallel with setup details.

Physical Standby :- Its a physical copy of the primary database. Till 10g the physical standby is kept open in "mount" mode so of actually no use other then a disaster recovery. But 11g onwards the physical standby database can also be used for queries and reporting as the open mode for the standby database can be "read_only".

For creating standby using RMAN, below can be the steps.

( Primary database is ORCL and standby is STANDBY in below example which is the db_unique_name for them, while ORACLE_SID and the DB_NAME is same i.e.ORCL)

Drop Database

To Drop a database we can directly use oracle command "Drop database". And this makes it easy enough clearing all the data and control files.

To drop the database we need to start the database in mount restricted mode.

The sequence of commands is as follows:-

Rename datafiles

Renaming may mostly mean moving a datafile. Moving a datafile may be a need of some scenario where the OS mount/drive is running out of space (as the datafile name involves the complete path), or files management etc.

For any of the case if we want to rename a datafile we have multiple approaches.
a. Taking Database Down
b. Taking Tablespace offline
c. Taking datafile offline

Locks in Database-2

Below is the query that can help you with multiple enqueue.

Locks in Database

Locks are mainly helpful to serialize jobs. Lock on a object is required by a session to update/edit the same, and if some other session wants to update it then it has to wait until earlier one releases the object and it comes to a consistent state.
This may be an object level enqueue to get the object edited by different sessions, or may be library lock/pin for the latch being used. But its dba who can decide what session should not be allowed to proceed or to be terminated taking others on priority.

Below are few of those tables and views that can help in identifying all kinds of locks

Direct Login to forms in eBusiness Suite

The usual url for loggin in to Oracle Application is
http://<server name>:<port>/
which most of the times gets directed to
http://<server name>:<port>/OA_HTML/AppsLocalLogin.jsp

But for some reason or for troubleshooting purpose we may need to login directly to forms.
Below are the urls for directly connecting forms.

RMAN-06091: no channel allocated for maintenance (of an appropriate type)

RMAN-06091: no channel allocated for maintenance (of an appropriate type)
The error message appears when we try to delete some backups. Set of commands could be like below.

RMAN> show retention policy;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
RMAN> delete obsolete;

Compile Database Objects - 1

There are multiple types of objects in database and different ways of compilation. There are different states for the objects and what we usually want them is to be "VALID".
To check the status of some object we can query user_objects, dba_objects views. Below query may show you the information required.

Tablespace Administration - 3

Temporary tablespace can be monitored/modified similarly, as we do for usual tablespaces. Use below links for details.
Tablespace Administration
Tablespace Administration with ASM
The difference here is the segments are temporary and are not being tracked by the views we have for other tablespaces.
For the files we have dba_temp_files and v$tempfile, and files are represented as tempfile at the place of datafile, and v$temp_space_header keeps track of free space.

So for the space and Usage we can have a query like below:-

Oracle Apps R12 Forms Not Opening

The forms for Oracle Apps EBS may not open for many reasons. Follow below steps to find out:-

Clear Cache bounce in R12

There are two ways to clear cache in R12.
1. Functional level (individual product/all product cache)
Functional Administrator -> Core Services -> Caching Framework -> Global Configuration -> "Go to specific cache or Clear All Cache"

2. Server level
In R12 apache bounce (which is actually opmn services here) takes a little more time then 11i, and we too have to take care of few things.
Basic steps for a clear cache bounce is as below:-
Set you application environment and go to $ADMIN_SCRIPTS_HOME

Tablespace Administration - 2

For ASM disks details you can use query as below.

column Name format A30
column Group_Number format 9999
column Path format A50
set linesize 150
select Name,Group_Number,Total_MB,Free_MB,PATH, Hot_Used_MB, Cold_Used_MB from v$asm_disk;

The Total Space details can be seen with below query.

R12 Blank Login Page

This may happen some times, mainly after the clone or even after some bounce.

There are multiple options to check, and try:-

11g alert log

The alert log location is obviously changed in 11g. The parameter that defines the top location ( Can be called ADR Base ) is "diagnostic_dest"

SQL> show parameter diag