Hendry's "Oracle and SQL Server DBA Stuff"

Oracle and SQL Server Database Solutions for DBA's please visit http://hendrydba.com for the latest posts. Thanks

Archive for June, 2010

Change Admin password in Apex

Posted by Hendry chinnapparaj on June 24, 2010

apex11g:/u01/oracle/product/11.2/apex> pwd

/u01/oracle/product/11.2/apex

apex11g:/u01/oracle/product/11.2/apex> ls -lrt apxchpwd.sql

-rw-r–r–    1 ofsad2   dba            1549 Jan  8 2009  apxchpwd.sql

apex11g:/u01/oracle/product/11.2/apex> sqlplus /nolog

SQL*Plus: Release 11.2.0.1.0 Production on Thu Jun 24 17:20:56 2010

Copyright (c) 1982, 2009, Oracle.  All rights reserved.

SQL> conn sys as sysdba

Enter password:

Connected.

SQL>

SQL>

SQL> show user

USER is “SYS”

SQL> @apxchpwd

Enter a value below for the password for the Application Express ADMIN user.

Enter a password for the ADMIN user              []

Session altered.

…changing password for ADMIN

PL/SQL procedure successfully completed.

Commit complete.

Then login to

http://devu0777.hiroshima.com:8080/apex/

and change the password for “admin” user as requested by the application.

Advertisements

Posted in Oracle Application Express 3.2 | Leave a Comment »

Failed to connect to database instance: ORA-28001: the password has expired (DBD ERROR: OCISessionBegin).

Posted by Hendry chinnapparaj on June 23, 2010

Oracle Enterprise Manager 10g Grid Control Alert

MessageFailed to connect to database instance: ORA-28001: the password has expired (DBD ERROR: OCISessionBegin).

SQL> select username, account_status from dba_users where username=’DBSNMP’;

USERNAME                       ACCOUNT_STATUS

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

DBSNMP                         EXPIRED

SQL> alter user dbsnmp identified by **** account unlock;

User altered.

And also update the dbsnmp password in the Grid control

http://srdu010.subiaco.com:4889/em/console/logon/logon

sysman

********

– click setup

– agents

under search, type the server name and click go

– click the server

– select radio button for the database instance name

– click configure

– change password

– test connection

– should get “The connection test was successful”

– click next

– submit

– fixed

Also restart the Grid Agent if needed

./emctl stop agent

./emctl start agent

Posted in EM10g Grid Control | 2 Comments »

Application Client Failover and DR Test

Posted by Hendry chinnapparaj on June 17, 2010

Application Client Failover and DR Test

Hendry Dasan – DBA

Thursday, 17 June 2010

Server and Database original setup Details

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

1.1     Environment Details – original setting

  • OS: IBM AIX 5.3 TL05
  • Hardware: IBM P-Series 595 Model
  • Oracle Software: Oracle 10gR2 Enterprise Edition -10204 (64bit)
  • ASM Oracle 11Gr2 Instance
  • Primary Site: 1 Node (DEVU009N3) – Dasan Street
  • Standby Site: 1 Node (DEVU009N4) – Christ Court
  • Storage: ASM11gR2
  • Database Name: CPSTEST
  • Instance Name: CPSTEST
  • Primary DB_UNIQUE_NAME: CPSTEST_J
  • Standby DB_UNIQUE_NAME: CPSTEST_F
  • Standby Type: Physical Standby

Tnsnames.ora setting in the  remote client

———————————————-

CPS =

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = devu009n3.greatwest.com)(PORT = 1521))

(ADDRESS = (PROTOCOL = TCP)(HOST = devu009n4.greatwest.com)(PORT = 1521))

)

(CONNECT_DATA =

(SERVICE_NAME = cps)

)

)

Data Guard Config Now

DGMGRL> show configuration;

Configuration

Name:                cpstest_dgb

Enabled:             YES

Protection Mode:     MaxAvailability

Fast-Start Failover: DISABLED

Databases:

cpstest_j – Physical standby database

cpstest_f – Primary database

Current status for “cpstest_dgb”:

SUCCESS

Note:_ the primary database is already at the DR Site- FC – before this exercise.

SQL> select host_name from v$instance;

HOST_NAME

—————————————————————-

devu009n4

SQL> select database_role,open_mode from v$database;

DATABASE_ROLE    OPEN_MODE

—————- ———-

PRIMARY          READ WRITE

SQL> show parameter service_name

NAME                                 TYPE        VALUE

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

service_names                        string      cps

INST_NAME

—————-

HOST_NAME

—————————————————————-

PROTECTION_MODE      SYNCHRONIZATION_STATUS LOG_ARCHIVED LOG_APPLIED

——————– ———————- ———— ———–

TIME_APPLIED      LOG_GAP

————– ———-

cpstest

devu009n4

MAXIMUM AVAILABILITY OK                              134         134

18/05 12:01:30          0

Connection from the remote client – pointing to primary database server (Christ court)

select host_name from v$instance;

HOST_NAME

—————————————————————-

devu009n4

SQL> select database_role,open_mode from v$database;

DATABASE_ROLE    OPEN_MODE

—————- ———-

PHYSICAL STANDBY MOUNTED

SQL> show parameter service_name

NAME                                 TYPE        VALUE

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

service_names                        string      cpstest_f

DOING A SWITCHOVER NOW from the current Primary Node(devu009n4) at Christ Court while the TOAD Client is still connected.

TEST1 à SWITCHOVER FROM CHRIST COURT TO DASAN STREET

DGMGRL> CONNECT SYS/CPSTEST

Connected.

DGMGRL> switchover to cpstest_j;

Performing switchover NOW, please wait…

Operation requires shutdown of instance “cpstest” on database “cpstest_f”

Shutting down instance “cpstest”…

ORA-01109: database not open

Database dismounted.

ORACLE instance shut down.

Operation requires shutdown of instance “cpstest” on database “cpstest_j”

Shutting down instance “cpstest”…

ORA-01109: database not open

Database dismounted.

ORACLE instance shut down.

Operation requires startup of instance “cpstest” on database “cpstest_f”

Starting instance “cpstest”…

ORACLE instance started.

Database mounted.

Operation requires startup of instance “cpstest” on database “cpstest_j”

Starting instance “cpstest”…

ORACLE instance started.

Database mounted.

Switchover succeeded, new primary is “cpstest_j”

DGMGRL>

SQL> select database_role,open_mode from v$database;

DATABASE_ROLE    OPEN_MODE

—————- ———-

PHYSICAL STANDBY MOUNTED

SQL> select host_name from v$instance;

HOST_NAME

—————————————————————-

devu009n4

SQL> show parameter service_name à Note:- the service_name changed back to cpstest_f in the standby role.

NAME                                 TYPE        VALUE

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

service_names                        string      cpstest_f

Connection from the remote TOAD client again – pointing to primary database server (Dasan Street)

select host_name from v$instance;

HOST_NAME

—————————————————————-

devu009n3

Also from the command prompt / remote sqlplus client connection to primary database

C:\Documents and Settings\bb15908>sqlplus dgtest/dgtest@cps

SQL*Plus: Release 10.2.0.4.0 – Production on Tue May 18 13:12:16 2010

Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.

Connected to:

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 – 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select host_name from v$instance;

HOST_NAME

—————————————————————-

devu009n3

Thursday, June 17, 2010

Query the new Primary database

SQL>  show parameter service_name à Note:- The Primary database always has the service_names as ”cps”

NAME                                 TYPE        VALUE

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

service_names                        string      cps

SQL> select database_role,open_mode from v$database;

DATABASE_ROLE    OPEN_MODE

—————- ———-

PRIMARY          READ WRITE

SQL> select host_name from v$instance;

HOST_NAME

—————————————————————-

devu009n3

Query the primary and standby database for any offline files

————————————————————-

select file#,name,status,checkpoint_change# from v$datafile where status not in (‘ONLINE’,’SYSTEM’)

no rows selected

NST_NAME

—————-

HOST_NAME

—————————————————————-

PROTECTION_MODE      SYNCHRONIZATION_STATUS LOG_ARCHIVED LOG_APPLIED

——————– ———————- ———— ———–

TIME_APPLIED      LOG_GAP

————– ———-

cpstest

devu009n4

MAXIMUM AVAILABILITY OK                              465         465

17/06 06:03:31          0

SQL> alter system switch logfile;

System altered.

select user from dual;

USER

——————————

CPS_OWNER

1 row selected.

select * from v$instance;

INSTANCE_NUMBER INSTANCE_NAME

————— —————-

HOST_NAME

—————————————————————-

VERSION           STARTUP_TIME STATUS       PARALLEL    THREAD# ARCHIVER

—————– ———— ———— ——– ———- ——–

LOG_SWITCH_WAIT LOGINS     SHUTDOWN_PENDING DATABASE_STATUS   INSTANCE_ROLE

————— ———- —————- —————– ——————

ACTIVE_STATE BLOCKED

———— ——-

1 cpstest

devu009n4

10.2.0.4.0        11-JUN-10    OPEN         NO                1 STARTED

ALLOWED    NO               ACTIVE            PRIMARY_INSTANCE

NORMAL       NO

1 row selected.

DGMGRL> show configuration;

Configuration

Name:                cpstest_dgb

Enabled:             YES

Protection Mode:     MaxAvailability

Fast-Start Failover: DISABLED

Databases:

cpstest_j – Physical standby database

cpstest_f – Primary database

Current status for “cpstest_dgb”:

SUCCESS

DGMGRL>

DGMGRL> switchover to cpstest_j;

Performing switchover NOW, please wait…

Operation requires shutdown of instance “cpstest” on database “cpstest_f”

Shutting down instance “cpstest”…

ORA-01109: database not open

Database dismounted.

ORACLE instance shut down.

Operation requires shutdown of instance “cpstest” on database “cpstest_j”

Shutting down instance “cpstest”…

ORA-01109: database not open

Database dismounted.

ORACLE instance shut down.

Operation requires startup of instance “cpstest” on database “cpstest_f”

Starting instance “cpstest”…

ORACLE instance started.

Database mounted.

Operation requires startup of instance “cpstest” on database “cpstest_j”

Starting instance “cpstest”…

ORACLE instance started.

Database mounted.

Switchover succeeded, new primary is “cpstest_j”

DGMGRL>

DGMGRL> show configuration;

Configuration

Name:                cpstest_dgb

Enabled:             YES

Protection Mode:     MaxAvailability

Fast-Start Failover: DISABLED

Databases:

cpstest_j – Primary database

cpstest_f – Physical standby database

Current status for “cpstest_dgb”:

SUCCESS

select * from v$instance;

INSTANCE_NUMBER INSTANCE_NAME

————— —————-

HOST_NAME

—————————————————————-

VERSION           STARTUP_TIME STATUS       PARALLEL    THREAD# ARCHIVER

—————– ———— ———— ——– ———- ——–

LOG_SWITCH_WAIT LOGINS     SHUTDOWN_PENDING DATABASE_STATUS   INSTANCE_ROLE

————— ———- —————- —————– ——————

ACTIVE_STATE BLOCKED

———— ——-

1 cpstest

devu009n3

10.2.0.4.0        17-JUN-10    OPEN         NO                1 STARTED

ALLOWED    NO               ACTIVE            PRIMARY_INSTANCE

NORMAL       NO

1 row selected.

select user from dual;

USER

——————————

CPS_OWNER

1 row selected.

Apps tested here – successfully connected to the other database.

SQL> alter system switch logfile;

System altered.

SQL> alter system checkpoint;

System altered.

SQL> alter system switch logfile;

System altered.

SQL> /

System altered.

SQL> /

System altered.

INST_NAME

—————-

HOST_NAME

—————————————————————-

PROTECTION_MODE      SYNCHRONIZATION_STATUS LOG_ARCHIVED LOG_APPLIED

——————– ———————- ———— ———–

TIME_APPLIED      LOG_GAP

————– ———-

cpstest

devu009n3

MAXIMUM AVAILABILITY OK                              475         475

17/06 13:56:23          0

Primary

————

SQL> select file#,name,status,checkpoint_change# from v$datafile where status not in (‘ONLINE’,’SYSTEM’);

no rows selected

SQL> select FLASHBACK_ON from v$database;

FLASHBACK_ON

——————

YES

SQL> select PROTECTION_MODE,PROTECTION_LEVEL from v$database;

PROTECTION_MODE      PROTECTION_LEVEL

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

MAXIMUM AVAILABILITY MAXIMUM AVAILABILITY

standby

———-

SQL> select file#,name,status,checkpoint_change# from v$datafile where status not in (‘ONLINE’,’SYSTEM’);

no rows selected

TEST1 à SWITCHOVER FROM CHRIST COURT TO DASAN STREET successfully completed

TEST2 à FAILOVER FROM DASAN STREET TO CHRIST COURT

Primary server Query

———————

DGMGRL> show configuration;

Configuration

Name:                cpstest_dgb

Enabled:             YES

Protection Mode:     MaxAvailability

Fast-Start Failover: DISABLED

Databases:

cpstest_j – Primary database

cpstest_f – Physical standby database

Current status for “cpstest_dgb”:

SUCCESS

FFF

SQL> select database_role,PROTECTION_MODE from v$database;

DATABASE_ROLE    PROTECTION_MODE

—————- ——————–

PRIMARY          MAXIMUM AVAILABILITY

SQL> select host_name from v$instance;

HOST_NAME

—————————————————————-

devu009n3

standby server Query

————————–

SQL> select database_role, open_mode from v$database;

DATABASE_ROLE    OPEN_MODE

—————- ———-

PHYSICAL STANDBY MOUNTED

SQL> select host_name from v$instance;

HOST_NAME

—————————————————————-

devu009n4

NOW KILL THE PRIMARY SERVER DEVU009N3 – CAN PULLOUT / DISABLE/ shutdown  THE NETWORK INTERFACE

After killing ther primary server, connect to dgmgrl tool in standby database –

may be a bit slow, but gets connected

– Now the primary server hangs / all the putty sessions hangs

STANDBY SERVER

DGMGRL> connect sys/cpstest

Connected.

DGMGRL> show configuration;

Configuration

Name:                cpstest_dgb

Enabled:             YES

Protection Mode:     MaxAvailability

Fast-Start Failover: DISABLED

Databases:

cpstest_j – Primary database

cpstest_f – Physical standby database

Current status for “cpstest_dgb”:

— JUST HANGS HERE IN STANDBY SERVER – DEVU009N4

Error: ORA-16662: network timeout when contacting a remote database

DGMGRL> DGMGRL>

DGMGRL> failover to cpstest_f;

Performing failover NOW, please wait…

Failover succeeded, new primary is “cpstest_f”

DGMGRL>

DGMGRL> show configuration;

Configuration

Name:                cpstest_dgb

Enabled:             YES

Protection Mode:     MaxPerformance

Fast-Start Failover: DISABLED

Databases:

cpstest_j – Physical standby database (disabled)

cpstest_f – Primary database

Current status for “cpstest_dgb”:

SUCCESS

SQL> select database_role, open_mode from v$database;

DATABASE_ROLE    OPEN_MODE

—————- ———-

PRIMARY          READ WRITE

SQL> select PROTECTION_MODE,PROTECTION_LEVEL from v$database;

PROTECTION_MODE      PROTECTION_LEVEL

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

MAXIMUM PERFORMANCE  MAXIMUM PERFORMANCE

select * from v$instance;

INSTANCE_NUMBER INSTANCE_NAME

————— —————-

HOST_NAME

—————————————————————-

VERSION           STARTUP_TIME STATUS       PARALLEL    THREAD# ARCHIVER

—————– ———— ———— ——– ———- ——–

LOG_SWITCH_WAIT LOGINS     SHUTDOWN_PENDING DATABASE_STATUS   INSTANCE_ROLE

————— ———- —————- —————– ——————

ACTIVE_STATE BLOCKED

———— ——-

1 cpstest

devu009n4

10.2.0.4.0        17-JUN-10    OPEN         NO                1 STARTED

ALLOWED    NO               ACTIVE            PRIMARY_INSTANCE

NORMAL       NO

1 row selected.

SQL> select file#,name,status,checkpoint_change# from v$datafile where status not in (‘ONLINE’,’SYSTEM’);

no rows selected

NOW BRING UP THE OLD PRIMARY SERVER – ENABLE NETWORK

INTERFACE

Reinstate the old primary as new standby

SQL> select database_role, open_mode from v$database;

DATABASE_ROLE    OPEN_MODE

—————- ———-

PRIMARY          READ WRITE

SQL> select host_name from v$instance;

HOST_NAME

—————————————————————-

devu009n3

SQL> shutdown immediate

Database closed.

Database dismounted.

ORACLE instance shut down.

SQL> startup mount

ORACLE instance started.

Total System Global Area  314572800 bytes

Fixed Size                  2083760 bytes

Variable Size             138413136 bytes

Database Buffers          171966464 bytes

Redo Buffers                2109440 bytes

Database mounted.

SQL> select flashback_on from v$database;

FLASHBACK_ON

——————

YES

SO CONNECT TO NEW PRIMARY DATABASE AND ISSUE THE BELOW FOR

REINSTATING THE OLD PRIMARY AS NEW STANDBY DATABASE

DGMGRL> connect sys/cpstest

Connected.

DGMGRL> reinstate database cpstest_j;

Reinstating database “cpstest_j”, please wait…

Operation requires shutdown of instance “cpstest” on database “cpstest_j”

Shutting down instance “cpstest”…

ORA-01109: database not open

Database dismounted.

ORACLE instance shut down.

Operation requires startup of instance “cpstest” on database “cpstest_j”

Starting instance “cpstest”…

ORACLE instance started.

Database mounted.

Continuing to reinstate database “cpstest_j” …

Reinstatement of database “cpstest_j” succeeded

DGMGRL> show configuration;

Configuration

Name:                cpstest_dgb

Enabled:             YES

Protection Mode:     MaxPerformance

Fast-Start Failover: DISABLED

Databases:

cpstest_j – Physical standby database

cpstest_f – Primary database

Current status for “cpstest_dgb”:

SUCCESS

NOW CONNECT TO THE NEW STANDBY DATABASE SERVER

SQL> select host_name from v$instance;

HOST_NAME

—————————————————————-

devu009n3

SQL> CONN / AS SYSDBA

Connected.

SQL> select name,status,checkpoint_change# from v$datafile where status not in

(‘ONLINE’,’SYSTEM’);  2

no rows selected

SQL> show parameter service_name

NAME                                 TYPE        VALUE

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

service_names                        string      cpstest_j

SQL> select database_role, open_mode from v$database;

DATABASE_ROLE    OPEN_MODE

—————- ———-

PHYSICAL STANDBY MOUNTED

GMGRL> connect sys/cpstest

Connected.

DGMGRL> show configuration;

Configuration

Name:                cpstest_dgb

Enabled:             YES

Protection Mode:     MaxPerformance

Fast-Start Failover: DISABLED

Databases:

cpstest_j – Physical standby database

cpstest_f – Primary database

Current status for “cpstest_dgb”:

SUCCESS

DGMGRL>

CONNECT TO PRIMARY AND SWITCH LOGS AND CHECK IF THEY ARE IN SYNC

SQL> alter system switch logfile;

System altered.

SQL> alter system checkpoint;

System altered.

SQL> alter system switch logfile;

System altered.

SQL> alter system switch logfile;

System altered.

INST_NAME

—————-

HOST_NAME

—————————————————————-

PROTECTION_MODE      SYNCHRONIZATION_STATUS LOG_ARCHIVED LOG_APPLIED

——————– ———————- ———— ———–

TIME_APPLIED      LOG_GAP

————– ———-

cpstest

devu009n4

MAXIMUM PERFORMANCE  CHECK CONFIGURATION               4           4

17/06 15:28:37          0

Note:- After the failover, the protection mode changes to maxperformance.

DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS MAXAVAILABILITY;

Succeeded.

DGMGRL> show configuration;

Configuration

Name:                cpstest_dgb

Enabled:             YES

Protection Mode:     MaxAvailability

Fast-Start Failover: DISABLED

Databases:

cpstest_j – Physical standby database

cpstest_f – Primary database

Current status for “cpstest_dgb”:

SUCCESS

INST_NAME

—————-

HOST_NAME

—————————————————————-

PROTECTION_MODE      SYNCHRONIZATION_STATUS LOG_ARCHIVED LOG_APPLIED

——————– ———————- ———— ———–

TIME_APPLIED      LOG_GAP

————– ———-

cpstest

devu009n4

MAXIMUM AVAILABILITY OK 33          33

21/06 14:48:59          0

1 row selected.

Check TOAD Connection

INSTANCE_NUMBER INSTANCE_NAME

————— —————-

HOST_NAME

—————————————————————-

VERSION           STARTUP_TIME STATUS       PARALLEL    THREAD# ARCHIVER

—————– ———— ———— ——– ———- ——–

LOG_SWITCH_WAIT LOGINS     SHUTDOWN_PENDING DATABASE_STATUS   INSTANCE_ROLE

————— ———- —————- —————– ——————

ACTIVE_STATE BLOCKED

———— ——-

1 cpstest

devu009n4

10.2.0.4.0        17-JUN-10    OPEN         NO                1 STARTED

ALLOWED    NO               ACTIVE            PRIMARY_INSTANCE

NORMAL       NO

1 row selected.

Apps tested here – successfully connected to the other database.

Shalom!

Posted in Data Guard and DR | Leave a Comment »

Archivelog Error in standby database ORA-00270, ORA-19809, ORA-19804

Posted by Hendry chinnapparaj on June 11, 2010

Problem

———–

The archive destination / FRA is full causing archive gap in the Data Guard Env.

Errors

——-

Creating archive destination file : +DATA (18727 blocks)

Fri Jun 11 15:07:29 2010

Errors in file /u01/oracle/product/10.2.0/db_1/admin/cpstest/udump/cpstest_rfs_344110.trc:

ORA-00270: error creating archive log +DATA

ORA-19809: limit exceeded for recovery files

ORA-19804: cannot reclaim 10485760 bytes disk space from 16106127360 limit

Fri Jun 11 15:07:29 2010

Errors in file /u01/oracle/product/10.2.0/db_1/admin/cpstest/udump/cpstest_rfs_344110.trc:

ORA-00270: error creating archive log +DATA

ORA-19809: limit exceeded for recovery files

ORA-19804: cannot reclaim 10485760 bytes disk space from 16106127360 limit

Query the Archive Gap

—————————-

SQL> SELECT ARCH.THREAD# “Thread”, ARCH.SEQUENCE# “Last Sequence Received”, APPL.SEQUENCE# “Last Sequence Applied”, (ARCH.SEQUENCE# – APPL.SEQUENCE#) “Difference”

2    FROM (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,

(SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL

3    4  WHERE ARCH.THREAD# = APPL.THREAD# ORDER BY 1;

Thread Last Sequence Received Last Sequence Applied Difference

———- ———————- ——————— ———-

1                    423                   259        164

Query the FRA Space

————————–

SQL> SELECT file_type, space_used * percent_space_used / 100 / 1024 / 1024 used,

space_reclaimable

* percent_space_reclaimable

/ 100

/ 1024

/ 1024 reclaimable,

frau.number_of_files

FROM v$recovery_file_dest rfd, v$flash_recovery_area_usage frau;

2    3    4    5    6    7    8

FILE_TYPE          USED RECLAIMABLE NUMBER_OF_FILES

———— ———- ———– —————

CONTROLFILE           0           0               0

ONLINELOG      909.1344           0               9

ARCHIVELOG   14415.6159           0             350

BACKUPPIECE     21.4998           0               2

IMAGECOPY             0           0               0

FLASHBACKLOG     7.6785           0               2

6 rows selected.

Fix the issue / delete the archivelog files which are already applied and reclaim disk space

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

Rman target /

RMAN> delete archivelog from sequence 1 until sequence 258;

deleted archive log

archive log filename=+DATA/cpstest_j/archivelog/2010_06_08/thread_1_seq_257.1686.721138949 recid=466 stamp=721138948

deleted archive log

archive log filename=+DATA/cpstest_j/archivelog/2010_06_08/thread_1_seq_258.1809.721139309 recid=467 stamp=721139309

Deleted 258 objects

Query FRA Space after deleting archive logs

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

SQL> SELECT file_type, space_used * percent_space_used / 100 / 1024 / 1024 used,

space_reclaimable

* percent_space_reclaimable

/ 100

/ 1024

/ 1024 reclaimable,

frau.number_of_files

FROM v$recovery_file_dest rfd, v$flash_recovery_area_usage frau;

2    3    4    5    6    7    8

FILE_TYPE          USED RECLAIMABLE NUMBER_OF_FILES

———— ———- ———– —————

CONTROLFILE           0           0               0

ONLINELOG      311.8656           0               9

ARCHIVELOG    1465.5576           0             224

BACKUPPIECE      7.3752       .0308               2

IMAGECOPY             0           0               0

FLASHBACKLOG    22.1256           0              16

6 rows selected.

Query for archive Gap

—————————-

SQL> SELECT ARCH.THREAD# “Thread”, ARCH.SEQUENCE# “Last Sequence Received”, APPL.SEQUENCE# “Last Sequence Applied”, (ARCH.SEQUENCE# – APPL.SEQUENCE#) “Difference”

2    FROM (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,

3    (SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL

4  WHERE ARCH.THREAD# = APPL.THREAD# ORDER BY 1;

Thread Last Sequence Received Last Sequence Applied Difference

———- ———————- ——————— ———-

1                    423                   423          0

devu009n4 $ dgmgrl /

DGMGRL for IBM/AIX RISC System/6000: Version 11.2.0.1.0 – 64bit Production

Copyright (c) 2000, 2009, Oracle. All rights reserved.

Welcome to DGMGRL, type “help” for information.

Connected.

DGMGRL> connect sys/cpstest

Connected.

DGMGRL> show configuration;

Error:

ORA-16525: the Data Guard broker is not yet available

Configuration details cannot be determined by DGMGRL

SQL> show parameter broker

NAME                                 TYPE        VALUE

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

dg_broker_config_file1               string      /u01/oracle/product/10.2.0/db_

1/dbs/dr1cpstest_f.dat

dg_broker_config_file2               string      /u01/oracle/product/10.2.0/db_

1/dbs/dr2cpstest_f.dat

dg_broker_start                      boolean     TRUE

primary

————

select synchronization_status, synchronized from v$archive_dest_Status;

SYNCHRONIZATION_STATUS SYNCHRONIZED

———————- ————

CHECK CONFIGURATION    NO

OK                     YES

CHECK CONFIGURATION    NO

CHECK CONFIGURATION    NO

CHECK CONFIGURATION    NO

CHECK CONFIGURATION    NO

CHECK CONFIGURATION    NO

CHECK CONFIGURATION    NO

evu009n3 $ dgmgrl

DGMGRL for IBM/AIX RISC System/6000: Version 10.2.0.4.0 – 64bit Production

Copyright (c) 2000, 2005, Oracle. All rights reserved.

Welcome to DGMGRL, type “help” for information.

DGMGRL> connect sys/cpstest

Connected.

DGMGRL> show configuration;

Configuration

Name:                cpstest_dgb

Enabled:             YES

Protection Mode:     MaxAvailability

Fast-Start Failover: DISABLED

Databases:

cpstest_j – Physical standby database

cpstest_f – Primary database

Current status for “cpstest_dgb”:

SUCCESS

DGMGRL>

devu009n4 $ . oraenv

ORACLE_SID = [+ASM] ? cpstest

The Oracle base for ORACLE_HOME=/u01/oracle/product/10.2.0/db_1 is /u01/oracle/product/10.2.0/db_1

devu009n4 $

devu009n4 $

devu009n4 $ dgmgrl /

DGMGRL for IBM/AIX RISC System/6000: Version 10.2.0.4.0 – 64bit Production

Copyright (c) 2000, 2005, Oracle. All rights reserved.

Welcome to DGMGRL, type “help” for information.

Connected.

DGMGRL> connect sys/cpstest

Connected.

DGMGRL> show configuration;

Configuration

Name:                cpstest_dgb

Enabled:             YES

Protection Mode:     MaxAvailability

Fast-Start Failover: DISABLED

Databases:

cpstest_j – Physical standby database

cpstest_f – Primary database

Current status for “cpstest_dgb”:

SUCCESS

DGMGRL>

Posted in Uncategorized | Leave a Comment »

ORA-19643: datafile 323: incremental-start SCN is too recent

Posted by Hendry chinnapparaj on June 4, 2010

Problem

———-

The incremental backup throws up ORA-19643 complaining on the datafile checkpoint SCN as older.

RMAN> BACKUP INCREMENTAL LEVEL 1 NOT BACKED UP SINCE TIME ‘SYSDATE-1/2’ DEVICE TYPE DISK CUMULATIVE DATABASE

FILESPERSET 8 FORMAT ‘/u03/oradata/flash_recovery_area/CPSOA1_JS/backupset/LF_%U’;

Starting backup at 03-06-2010 18:22:56

allocated channel: ORA_DISK_1

channel ORA_DISK_1: sid=702 devtype=DISK

channel ORA_DISK_1: starting compressed incremental level 1 datafile backupset

channel ORA_DISK_1: specifying datafile(s) in backupset

input datafile fno=00023 name=/u02/oradata/cpsoa1/BWA_LM_DATA_64M_02.DBF

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/03/2010 18:23:42

ORA-19643: datafile 323: incremental-start SCN is too recent

ORA-19640: datafile checkpoint is SCN 18624685831 time 04/07/2009 15:15:04

Solution

————

Do the backup based on the SCN time in the error above, which takes care of the other datafiles as well.

RMAN> BACKUP INCREMENTAL FROM SCN 18624685831 DEVICE TYPE DISK CUMULATIVE DATABASE FILESPERSET 8 FORMAT ‘/u03/oradata/flash_recovery_area/CPSOA1_JS/backupset/LF_%U’;

Starting backup at 03-06-2010 18:59:28

using channel ORA_DISK_1

RMAN-06755: WARNING: datafile 269: incremental-start SCN is too recent; using checkpoint SCN 18624685314 instead

RMAN-06755: WARNING: datafile 270: incremental-start SCN is too recent; using checkpoint SCN 18624685323 instead

RMAN-06755: WARNING: datafile 271: incremental-start SCN is too recent; using checkpoint SCN 18624685332 instead

RMAN-06755: WARNING: datafile 272: incremental-start SCN is too recent; using checkpoint SCN 18624685341 instead

RMAN-06755: WARNING: datafile 273: incremental-start SCN is too recent; using checkpoint SCN 18624685351 instead

RMAN-06755: WARNING: datafile 274: incremental-start SCN is too recent; using checkpoint SCN 18624685360 instead

RMAN-06755: WARNING: datafile 275: incremental-start SCN is too recent; using checkpoint SCN 18624685370 instead

RMAN-06755: WARNING: datafile 276: incremental-start SCN is too recent; using checkpoint SCN 18624685379 instead

RMAN-06755: WARNING: datafile 277: incremental-start SCN is too recent; using checkpoint SCN 18624685389 instead

RMAN-06755: WARNING: datafile 278: incremental-start SCN is too recent; using checkpoint SCN 18624685399 instead

RMAN-06755: WARNING: datafile 279: incremental-start SCN is too recent; using checkpoint SCN 18624685408 instead

RMAN-06755: WARNING: datafile 280: incremental-start SCN is too recent; using checkpoint SCN 18624685417 instead

RMAN-06755: WARNING: datafile 281: incremental-start SCN is too recent; using checkpoint SCN 18624685426 instead

RMAN-06755: WARNING: datafile 282: incremental-start SCN is too recent; using checkpoint SCN 18624685436 instead

RMAN-06755: WARNING: datafile 283: incremental-start SCN is too recent; using checkpoint SCN 18624685446 instead

RMAN-06755: WARNING: datafile 284: incremental-start SCN is too recent; using checkpoint SCN 18624685456 instead

RMAN-06755: WARNING: datafile 285: incremental-start SCN is too recent; using checkpoint SCN 18624685465 instead

RMAN-06755: WARNING: datafile 286: incremental-start SCN is too recent; using checkpoint SCN 18624685475 instead

RMAN-06755: WARNING: datafile 287: incremental-start SCN is too recent; using checkpoint SCN 18624685484 instead

RMAN-06755: WARNING: datafile 288: incremental-start SCN is too recent; using checkpoint SCN 18624685494 instead

RMAN-06755: WARNING: datafile 289: incremental-start SCN is too recent; using checkpoint SCN 18624685504 instead

RMAN-06755: WARNING: datafile 290: incremental-start SCN is too recent; using checkpoint SCN 18624685514 instead

RMAN-06755: WARNING: datafile 291: incremental-start SCN is too recent; using checkpoint SCN 18624685523 instead

RMAN-06755: WARNING: datafile 292: incremental-start SCN is too recent; using checkpoint SCN 18624685532 instead

RMAN-06755: WARNING: datafile 293: incremental-start SCN is too recent; using checkpoint SCN 18624685542 instead

RMAN-06755: WARNING: datafile 294: incremental-start SCN is too recent; using checkpoint SCN 18624685552 instead

RMAN-06755: WARNING: datafile 295: incremental-start SCN is too recent; using checkpoint SCN 18624685561 instead

RMAN-06755: WARNING: datafile 296: incremental-start SCN is too recent; using checkpoint SCN 18624685571 instead

RMAN-06755: WARNING: datafile 297: incremental-start SCN is too recent; using checkpoint SCN 18624685580 instead

RMAN-06755: WARNING: datafile 298: incremental-start SCN is too recent; using checkpoint SCN 18624685590 instead

RMAN-06755: WARNING: datafile 299: incremental-start SCN is too recent; using checkpoint SCN 18624685599 instead

RMAN-06755: WARNING: datafile 300: incremental-start SCN is too recent; using checkpoint SCN 18624685608 instead

RMAN-06755: WARNING: datafile 301: incremental-start SCN is too recent; using checkpoint SCN 18624685617 instead

RMAN-06755: WARNING: datafile 302: incremental-start SCN is too recent; using checkpoint SCN 18624685627 instead

RMAN-06755: WARNING: datafile 303: incremental-start SCN is too recent; using checkpoint SCN 18624685637 instead

RMAN-06755: WARNING: datafile 304: incremental-start SCN is too recent; using checkpoint SCN 18624685647 instead

RMAN-06755: WARNING: datafile 305: incremental-start SCN is too recent; using checkpoint SCN 18624685656 instead

RMAN-06755: WARNING: datafile 306: incremental-start SCN is too recent; using checkpoint SCN 18624685666 instead

RMAN-06755: WARNING: datafile 307: incremental-start SCN is too recent; using checkpoint SCN 18624685677 instead

RMAN-06755: WARNING: datafile 308: incremental-start SCN is too recent; using checkpoint SCN 18624685687 instead

RMAN-06755: WARNING: datafile 309: incremental-start SCN is too recent; using checkpoint SCN 18624685696 instead

RMAN-06755: WARNING: datafile 310: incremental-start SCN is too recent; using checkpoint SCN 18624685706 instead

RMAN-06755: WARNING: datafile 311: incremental-start SCN is too recent; using checkpoint SCN 18624685715 instead

RMAN-06755: WARNING: datafile 312: incremental-start SCN is too recent; using checkpoint SCN 18624685725 instead

RMAN-06755: WARNING: datafile 313: incremental-start SCN is too recent; using checkpoint SCN 18624685735 instead

RMAN-06755: WARNING: datafile 314: incremental-start SCN is too recent; using checkpoint SCN 18624685744 instead

RMAN-06755: WARNING: datafile 315: incremental-start SCN is too recent; using checkpoint SCN 18624685753 instead

RMAN-06755: WARNING: datafile 316: incremental-start SCN is too recent; using checkpoint SCN 18624685763 instead

RMAN-06755: WARNING: datafile 317: incremental-start SCN is too recent; using checkpoint SCN 18624685773 instead

RMAN-06755: WARNING: datafile 318: incremental-start SCN is too recent; using checkpoint SCN 18624685783 instead

RMAN-06755: WARNING: datafile 319: incremental-start SCN is too recent; using checkpoint SCN 18624685793 instead

RMAN-06755: WARNING: datafile 320: incremental-start SCN is too recent; using checkpoint SCN 18624685803 instead

RMAN-06755: WARNING: datafile 321: incremental-start SCN is too recent; using checkpoint SCN 18624685813 instead

RMAN-06755: WARNING: datafile 322: incremental-start SCN is too recent; using checkpoint SCN 18624685822 instead

channel ORA_DISK_1: starting compressed full datafile backupset

channel ORA_DISK_1: specifying datafile(s) in backupset

input datafile fno=00023 name=/u02/oradata/cpsoa1/BWA_LM_DATA_64M_02.DBF

input datafile fno=00323 name=/u04/oradata/cpsoa1/CB055_01.DBF

skipping datafile 00323 because it has not changed

input datafile fno=00346 name=/u04/oradata/cpsoa1/CB078_01.DBF

input datafile fno=00222 name=/u02/oradata/cpsoa1/CSHTRAP.DBF

input datafile fno=00120 name=/u02/oradata/cpsoa1/CPS_LM_DATA_64M_01.DBF

channel ORA_DISK_1: starting piece 1 at 03-06-2010 18:59:37

Posted in RMAN10G | Leave a Comment »

Run Database Health Check using DBMS_HM PL/SQL Package

Posted by Hendry chinnapparaj on June 2, 2010

To obtain a list of health check names, run the following query:

SELECT name FROM v$hm_check WHERE internal_check='N';

SQL> SELECT name FROM v$hm_check WHERE internal_check=’N’;

NAME

—————————————————————-

DB Structure Integrity Check

CF Block Integrity Check

Data Block Integrity Check

Redo Integrity Check

Transaction Integrity Check

Undo Segment Integrity Check

Dictionary Integrity Check

ASM Allocation Check

8 rows selected.

Running Health Checks Using the DBMS_HM PL/SQL Package

The DBMS_HM procedure for running a health check is called RUN_CHECK. To call RUN_CHECK, supply the name of the check and a name for the run, as follows:

SQL> BEGIN

2      DBMS_HM.RUN_CHECK(‘Dictionary Integrity Check’, ‘my_run’);

3  END;

4  /

PL/SQL procedure successfully completed.

set pages 1000 lines 160

column check_name format a30

column parameter_name format a20

column default_value format a20

column description format a40

SELECT c.name check_name, p.name parameter_name, p.type,

p.default_value, p.description

FROM v$hm_check_param p, v$hm_check c

WHERE p.check_id = c.id and c.internal_check = ‘N’

ORDER BY c.name;

CHECK_NAME                     PARAMETER_NAME       TYPE                 DEFAULT_VALUE        DESCRIPTION

—————————— ——————– ——————– ——————– —————————————-

ASM Allocation Check           ASM_DISK_GRP_NAME    DBKH_PARAM_TEXT                           ASM group name

CF Block Integrity Check       CF_BL_NUM            DBKH_PARAM_UB4                            Control file block number

Data Block Integrity Check     BLC_DF_NUM           DBKH_PARAM_UB4                            File number

Data Block Integrity Check     BLC_BL_NUM           DBKH_PARAM_UB4                            Block number

Dictionary Integrity Check     CHECK_MASK           DBKH_PARAM_TEXT      ALL                  Check mask

Dictionary Integrity Check     TABLE_NAME           DBKH_PARAM_TEXT      ALL_CORE_TABLES      Table name

Redo Integrity Check           SCN_TEXT             DBKH_PARAM_TEXT      0                    SCN of the latest good redo (if known)

Transaction Integrity Check    TXN_ID               DBKH_PARAM_TEXT                           Transaction ID

Undo Segment Integrity Check   USN_NUMBER           DBKH_PARAM_TEXT                           Undo segment number

9 rows selected.

Viewing Reports Using the ADRCI Utility

You can create and view Health Monitor checker reports using the ADRCI utility.

To create and view a checker report using ADRCI

  1. Ensure that operating system environment variables (such as ORACLE_HOME) are set properly, and then enter the following command at the operating system command prompt:
2.         ADRCI

The utility starts and displays the following prompt:

adrci>>

adrci> show hm_run

ADR Home = c:\app\oracle\diag\clients\user_bb15908\host_3515219834_76:

*************************************************************************

0 rows fetched

<ADR_RELATION>

<ADR_HOME name=”c:\app\oracle\diag\clients\user_bb15908\host_3515219834_76″>

ADR Home = c:\app\oracle\diag\clients\user_unknown\host_3515219834_76:

*************************************************************************

0 rows fetched

</ADR_HOME>

<ADR_HOME name=”c:\app\oracle\diag\clients\user_unknown\host_3515219834_76″>

ADR Home = c:\app\oracle\diag\rdbms\oracle11g\oracle11g:

*************************************************************************

**********************************************************

HM RUN RECORD 1

**********************************************************

RUN_ID                        1

RUN_NAME                      HM_RUN_1

CHECK_NAME                    DB Structure Integrity Check

NAME_ID                       2

MODE                          2

START_TIME                    2010-05-24 07:52:24.556000 +08:00

RESUME_TIME                   <NULL>

END_TIME                      2010-05-24 07:52:26.478000 +08:00

MODIFIED_TIME                 2010-05-24 07:52:26.478000 +08:00

TIMEOUT                       0

FLAGS                         0

STATUS                        6

SRC_INCIDENT_ID               0

NUM_INCIDENTS                 0

ERR_NUMBER                    210

REPORT_FILE                   <NULL>

**********************************************************

HM RUN RECORD 2

**********************************************************

RUN_ID                        21

RUN_NAME                      HM_RUN_21

CHECK_NAME                    DB Structure Integrity Check

NAME_ID                       2

MODE                          2

START_TIME                    2010-05-24 17:08:21.525000 +08:00

RESUME_TIME                   <NULL>

END_TIME                      2010-05-24 17:08:23.150000 +08:00

MODIFIED_TIME                 2010-05-24 17:08:23.150000 +08:00

TIMEOUT                       0

FLAGS                         0

STATUS                        6

SRC_INCIDENT_ID               0

NUM_INCIDENTS                 0

ERR_NUMBER                    210

REPORT_FILE                   <NULL>

**********************************************************

HM RUN RECORD 3

**********************************************************

RUN_ID                        41

RUN_NAME                      HM_RUN_41

CHECK_NAME                    DB Structure Integrity Check

NAME_ID                       2

MODE                          2

START_TIME                    2010-05-31 22:00:03.194000 +08:00

RESUME_TIME                   <NULL>

END_TIME                      2010-05-31 22:00:05.085000 +08:00

MODIFIED_TIME                 2010-05-31 22:00:05.085000 +08:00

TIMEOUT                       0

FLAGS                         0

STATUS                        5

SRC_INCIDENT_ID               0

NUM_INCIDENTS                 0

ERR_NUMBER                    0

REPORT_FILE                   <NULL>

**********************************************************

HM RUN RECORD 4

**********************************************************

RUN_ID                        61

RUN_NAME                      HM_RUN_61

CHECK_NAME                    DB Structure Integrity Check

NAME_ID                       2

MODE                          2

START_TIME                    2010-05-31 22:00:05.397000 +08:00

RESUME_TIME                   <NULL>

END_TIME                      2010-05-31 22:00:06.585000 +08:00

MODIFIED_TIME                 2010-05-31 22:00:06.585000 +08:00

TIMEOUT                       0

FLAGS                         0

STATUS                        5

SRC_INCIDENT_ID               0

NUM_INCIDENTS                 0

ERR_NUMBER                    0

REPORT_FILE                   <NULL>

**********************************************************

HM RUN RECORD 5

**********************************************************

RUN_ID                        81

RUN_NAME                      my_run

CHECK_NAME                    Dictionary Integrity Check

NAME_ID                       24

MODE                          0

START_TIME                    2010-06-02 14:52:41.657000 +08:00

RESUME_TIME                   <NULL>

END_TIME                      2010-06-02 14:52:48.172000 +08:00

MODIFIED_TIME                 2010-06-02 14:59:47.235000 +08:00

TIMEOUT                       0

FLAGS                         0

STATUS                        5

SRC_INCIDENT_ID               0

NUM_INCIDENTS                 0

ERR_NUMBER                    0

REPORT_FILE                   c:\app\oracle\diag\rdbms\oracle11g\oracle11g\hm\HMREPORT_my_run.hm

5 rows fetched

Health Monitor Views

Instead of requesting a checker report, you can view the results of a specific checker run by directly querying the ADR data from which reports are created. This data is available through the views V$HM_RUN, V$HM_FINDING, and V$HM_RECOMMENDATION.

The following example queries the V$HM_RUN view to determine a history of checker runs:

SQL> SELECT run_id, name, check_name, run_mode, src_incident FROM v$hm_run;

RUN_ID NAME                             CHECK_NAME

———- ——————————– ——————————–

RUN_MODE SRC_INCIDENT

——– ————

21 HM_RUN_21                        DB Structure Integrity Check

REACTIVE            0

41 HM_RUN_41                        DB Structure Integrity Check

REACTIVE            0

61 HM_RUN_61                        DB Structure Integrity Check

REACTIVE            0

RUN_ID NAME                             CHECK_NAME

———- ——————————– ——————————–

RUN_MODE SRC_INCIDENT

——– ————

81 my_run                           Dictionary Integrity Check

MANUAL              0

1 HM_RUN_1                         DB Structure Integrity Check

REACTIVE            0

The next example queries the V$HM_FINDING view to obtain finding details for the reactive data block check with RUN_ID 21

SQL> SELECT type, description FROM v$hm_finding WHERE run_id = 21;

no rows selected

Posted in Uncategorized | Leave a Comment »

Create Oracle Application Express Workspace

Posted by Hendry chinnapparaj on June 2, 2010

Create Oracle Application Express Workspace

http://lap6467.rtdomau.local:8080/apex/apex_admin

admin

apex123?

Manage workspace à create workspace à

Workspace Name à apollo

Description à This is a test workspace à

Schema name à apollo

Password à apollo à

Administrator username à admin

Administrator password à apex123?

Email à Hendry@oracle.com

Create à done

Workspace successfully provisioned.

Workspace apollo provisioned with administrator ADMIN.

Database user APOLLO created with default tablespace FLOW_1048601238028425 using datafile H:\APP\ORACLE\ORADATA\ORACLE11G\FLOW_1048601238028425.DBF

Logout

You are now logged out.

Login

Wokspace à apollo

username à apollo

password à apollo

Posted in Oracle Application Express 3.2 | Leave a Comment »

Configure the Embedded PL/SQL Gateway in oracle11Gr2

Posted by Hendry chinnapparaj on June 2, 2010

Configure the Embedded PL/SQL Gateway in oracle11gR2

C:\app\oracle\product\11.2.0\dbhome_1\apex>sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Mon May 31 16:06:26 2010

Copyright (c) 1982, 2010, Oracle.  All rights reserved.

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> connect sys as sysdba

Enter password:

Connected.

SQL> show user

USER is “SYS”

Running the apxconf.sql Configuration Script

SQL> @apxconf

PORT

———-

8080

Enter values below for the XDB HTTP listener port and the password for the Application Express ADMIN

user.

Default values are in brackets [ ].

Press Enter to accept the default value.

Enter a password for the ADMIN user              [] apex123

Enter a port for the XDB HTTP listener [      8080]

…changing HTTP Port

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

Session altered.

…changing password for ADMIN

PL/SQL procedure successfully completed.

Commit complete.

SQL> ALTER USER ANONYMOUS ACCOUNT UNLOCK;

User altered.

Verifying the Oracle XML DB HTTP Server Port

SQL> SELECT DBMS_XDB.GETHTTPPORT FROM DUAL;

GETHTTPPORT

———–

8080

If the port number returns 0, the Oracle XML DB HTTP Server is disabled.

SQL> show parameter compatible

NAME                                 TYPE        VALUE

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

compatible                           string      11.2.0.0.0

Posted in Oracle Application Express 3.2 | Leave a Comment »

Getting Error ‘Invalid Login Credentials’ After Creating A New Workspace

Posted by Hendry chinnapparaj on June 2, 2010

Problem

When trying to login as the new user, getting the Invalid login credentials in the browser

Cause

User attributes for the workspace are not modified correctly under the option “Manage Application Developers” under heading “Manage Workspaces”.

Fix

Follow the steps mentioned below after creating the workspace with a new user.

1. Login as “Admin” user.

http://lap45365787.stdomau.local:8080/apex/apex_admin
2. On the “Home” page, you can see the option “Manage Developers and users” under heading
“Manage Workspaces”.
3. Click on the option “Manage Developers and users”.
4. Click on the “Edit” link for the user “Apollo”.
5. Edit “User Attributes” -> Set User Name to Apollo, add the “Web Password” as Apollo (Passwords
are case sensitive) and set the Developer privileges.

Then try logging into workspace “apollo” with “apollo/apollo” and it will login successfully.

http://lap45365787.stdomau.local:8080/apex/

workspace – Apollo

username – Apollo

password – Apollo

Posted in Oracle Application Express 3.2 | Leave a Comment »