Friday, November 22, 2013

ORA-00376: file 5 cannot be read at this time,ORA-01157: cannot identify/lock data file 5

Recovering the Database After the Loss of the SYSTEM or UNDO
Tablespace Datafile

In this case, we will just restore the tablespaces or datafiles that were lost. Of course,because these are critical tablespace objects, the database itself is down. After restoring the datafiles that were lost (do not restore any datafiles that are intact), recover the databasefollowing these steps:

1. Log into the database as SYS.

2. Mount the database with the startup mount command.

3. For recovery, you have two options. You can use the recover tablespace or the recoverdatafile command to recover the datafiles that were lost. It’s kind of up to you which one you want to use (we like the recover tablespace command in this situation more).

4. The recover database command will recommend to you the correct archived redo log to apply. At the prompt, type AUTO; the recover database command automatically starts applying all redo until the database is recovered.

5. Once database recovery is complete, the recover database command will return you to the  SQL prompt. You can then issue the alter database open command to open the database for business.

{
Recovery of the UNDO Tablespace
There are cases where the UNDO tablespace can be recovered online. If the database was shut down in a consistent manner before the UNDO tablespace was lost, it may be that all you will need to do is take the UNDO tablespace datafiles offline (you won’t be able to take the tablespace itself offline) and then open the database.Oracle has a default SYSTEM tablespace that would be used in this case, when the database initially comes up. You could then just create a new UNDO tablespace and drop the old one. This might be a quicker recovery method in some cases.
}

If the tablespace/datafile you lost is not associated with the SYSTEM or UNDO tablespaces,
then you are in luck. You don’t even need to shut down the database to recover! All you
need to do is take the datafiles offline, restore the impacted datafiles, recover the datafiles
(or the tablespace), and bring them back online.

The nice thing about this is if your users are not using the tablespace, they will never
know there was a problem. If the users are using the tablespace, they will be impacted only
if they try to use the datafiles that are offline (which is one good reason in some cases to
take just datafiles offline rather than the whole tablespace).

The first question is, How do you know which datafiles are missing? There are a couple
of things that will give you a clue. First of all, your users will start getting these messages:

SQL> select * from corporate.stockvalue;
select * from corporate.stockvalue

ERROR at line 1:
ORA-00376: file 5 cannot be read at this time
ORA-01110: data file 5: ‘D:\APP\ADMINISTRATOR\ORADATA\TEST\AXPERT04.DBF’


You can also look at the V$RECOVER_FILE view for more information on datafiles that
need recovery. Here is an example of such a query:

SQL> select * from v$recover_file;

FILE#     ONLINE                 ONLINE_               ERROR                                  CHANGE#            TIME
----------   -------                       -------                       --------------------                      ----------                  ---------
        5      ONLINE                 ONLINE                 FILE NOT FOUND                    0         

{
Missing Datafiles
Don’t expect that these errors indicating datafiles are missing will always show up in thealert log. Sometimes they will (for example, on database startup), but often they won’t (for example, when a query fails because a datafile is offline). If you want to monitor for this problem reliably, then the V$RECOVER_FILE view is the way to go.
}

So, here is the general recovery process from such an error. In this case we assume the
database is up and running:
1. Take the datafile offline using the alter database datafile offline command as
shown here:

alter database datafile ‘D:\APP\ADMINISTRATOR\ORADATA\TEST\AXPERT04.DBF’ offline;

As an alternative, you can use FILE_ID as shown in this example:
alter database datafile 5 offline;

FILE_ID will appear in the error message, or you can use the FILE_ID column of
DBA_DATA_FILES or the FILE# column in the V$DATAFILE view.

2. Restore the missing datafiles.


3. Restore all archived redo logs that will be needed for recovery. This would be all
archived redo logs generated from the beginning of the backup image you restored
in step 2.

Warning
When you are restoring backup files, never restore backed-up online redo
logs over the existing online redo logs. This is so important.we did not even back up the online redo logs. Restoring old online redo logs over your existing ones will lead to data loss. Fair warning!

4. Recover the missing datafiles with the recover datafile or recover tablespace command.

5. Bring the datafiles or the tablespace online with the alter database or alter tablespace ommand.So, what do you do if your database was down and you discover the files are lost when you start it up? That’s simple too.

1. Log in as SYS and start up the database. If a datafile is missing, you will get an error message that looks something like this:

SQL> startup
ORACLE instance started.
Total System Global Area 397557760 bytes
Fixed Size 1333452 bytes
Variable Size 289408820 bytes
Database Buffers 100663296 bytes
Redo Buffers 6152192 bytes
Database mounted.
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: ‘D:\APP\ADMINISTRATOR\ORADATA\TEST\AXPERT04.DBF’

2. It may be that you are missing more than datafile 4, since Oracle will alert you toonly the first datafile that it finds missing. Use the V$RECOVER_FILE, V$DATAFILE,and V$TABLESPACE views to determine exactly which datafiles are missing and which tablespaces they are associated with, as shown in this example:

SQL> select b.name ts_name, a.error, c.name datafile
2 from v$recover_file a, v$tablespace b, v$datafile c
3 where a.file#=c.file# and b.ts#=c.ts#
SQL> /

TS_NAME     ERROR                            DATAFILE
---------          --------------------                ------------------------------------
AXPERT       FILE NOT FOUND          D:\APP\ADMINISTRATOR\ORADATA\TEST\AXPERT04.DBF

3. Review the results of the query. As long as the missing datafiles are not part of the SYSTEM
or UNDO tablespace, you can simply take those datafiles offline and open the database. The
intent will be to recover those tablespaces/datafiles with the database open. First use the alter database datafile offline command to take the tablespaces offline:

SQL> alter database datafile ‘D:\APP\ADMINISTRATOR\ORADATA\TEST\AXPERT04.DBF’ offline;
Database altered.

4. Next, open the database with the alter database open command:
alter database open

5. Now restore the database backup datafiles from your hot backup media.

6. Restore all archived redo logs that will be needed for recovery. You will need to restore
all archived redo logs generated from the beginning of the backup image you restored in step 2.

Figuring Out Which Archived Redo Logs You Need
If you need to figure out exactly which archived redo logs you need to restore your backup (so, perhaps, you can restore those files off of backup media), you can use the V$RECOVER_FILE and the V$LOG_HISTORY views. The V$RECOVER_FILE view provides the last change number (in the CHANGE# column) present in the file(s) needing recovery. The V$LOG_HISTORY view will tell you which archived redo logs the changes are in. Here is an example:

ORA-01157: cannot identify/lock data file 5 - see DBWR trace file 
ORA-01110: data file 5: ‘D:\APP\ADMINISTRATOR\ORADATA\TEST\AXPERT04.DBF’

SQL> host copy AXPERT04.DBF.BKP AXPERT04.DBF
1 file(s) copied.

SQL> Select a.file#, a.change#, b.first_change#, b.next_change#, b.sequence#
2 From v$recover_file a, v$log_history b Where a.change#<=b.next_change#;

FILE#    CHANGE#            FIRST_CHANGE#             NEXT_CHANGE#              SEQUENCE#
---------- ----------                    -------------                               ------------                               ----------
5              1418889                1417349                                1438925                                20

7. Recover the datafiles or tablespaces using the recover datafile or recover tablespace command.

SQL> recover datafile 5;

8. Bring the datafiles or tablespaces online using the alter database datafile online or alter tablespace online command. Once you have done this, you have recovered the missing tablespace datafiles and your database is back to normal.

SQL>Alter database datafile 5 online;

Recovering the Database After the Loss of All Datafiles

Recovering the Database After the Loss of All Datafiles

You can use the recover database command to recover the entire database all at once.
Having restored all the database datafiles from the backup media, you would follow
these steps:

1. Log into the database as SYS.

2. Mount the database with the startup mount command.

3. Issue the recover database command from the SQL prompt.

4. The recover database command will recommend to you the correct archived redo log to apply. At the prompt,   type AUTO; the recover database command automatically starts applying all redo until the database is recovered.

5. Once database recovery is complete, the recover database command will return you to the SQL prompt. You can then issue the alter database open command to open the database for business.

1. Back up the database. Details on how to do a full online database backup are found in

2. In summary, follow these steps:

Ø  First put the database in hot backup mode.
Ø  Copy all database datafiles to a backup location.
Ø  Take the database out of hot backup mode.
Ø  Force a log switch. Back up the archived redo logs.

Here is an example of a backup:

C:\Users\Administrator>sqlplus

SQL*Plus: Release 11.2.0.3.0 Production on Fri Nov 22 14:14:31 2013

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

Enter user-name: sys@test as sysdba
Enter password:

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> alter database begin backup;
Database altered.
SQL> host copy D:\app\Administrator\oradata\TEST \*.dbf  E:\HOT_BACKUP
SQL> alter database end backup;
Database altered.
SQL> alter system switch logfile;
System altered.
SQL> host copy D:\app\Administrator\fast_recovery_area\TEST\ARCHIVELOG\2013_10_31\*.ARC       E:\HOT_BACKUP\ARCHIVELOG
SQL> alter database backup controlfile to trace;
Database altered.
SQL> alter database backup controlfile to ‘E:\HOT_BACKUP\control1.bak’;
Database altered.

3. Now remove all datafiles from the database. On some operating-system platforms (Linux, for example), you can do this with the database up and running, and on others (Windows) you will have to shut down the database.


SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.

5. Once you are sure the database is down, move old datafiles to some other location abd restore the database datafiles from their  backup location to the location where the database files belong.

6. Now connect to the database and issue the startup mount command.

C:\Users\Administrator>sqlplus
SQL*Plus: Release 11.2.0.3.0 Production on Fri Nov 22 14:14:31 2013
Copyright (c) 1982, 2011, Oracle.  All rights reserved.
Enter user-name: sys@test as sysdba
Enter password:
Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Connected to an idle instance.

SQL> startup
ORACLE instance started.

Total System Global Area 1.1758E+10 bytes
Fixed Size                  2265896 bytes
Variable Size            8522829016 bytes
Database Buffers         3221225472 bytes
Redo Buffers               12099584 bytes
Database mounted.

7. To recover the database, issue the recover database command. The command may return a response that says “media recovery complete,” as shown here:

SQL> recover database;

You may also be prompted to apply archived redo logs. Simply enter AUTO at the prompt.

SQL> recover database;
ORA-00279: change 5071334 generated at 08/17/2008 15:35:51 needed for thread 1
ORA-00289: suggestion :
D:\app\Administrator\fast_recovery_area\TEST\ARCHIVELOG \2008_08_17/o1_mf_1_5_4bk6onh8_.arcORA-00280:
change 5071334 for thread 1 is in sequence #5
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 5071583 generated at 08/17/2008
15:40:04 needed for thread 1
ORA-00289: suggestion :
D:\app\Administrator\fast_recovery_area\TEST\ARCHIVELOG \2008_08_17/o1_mf_1_6_4bk76kwk_.arcORA-00280:
change 5071583 for thread 1 is in sequence #6
ORA-00279: change 5091960 generated at 08/17/2008
15:49:05 needed for thread 1
ORA-00289: suggestion :
D:\app\Administrator\fast_recovery_area\TEST\ARCHIVELOG \2008_08_17/o1_mf_1_7_4bk9ksb4_.arcORA-00280:
change 5091960 for thread 1 is in sequence #7
ORA-00279: change 5112317 generated at 08/17/2008
16:29:13 needed for thread 1
ORA-00289: suggestion :
D:\app\Administrator\fast_recovery_area\TEST\ARCHIVELOG \2008_08_17/o1_mf_1_8_4bk9p236_.arcORA-00280:
change 5112317 for thread 1 is in sequence #8
ORA-00279: change 5112647 generated at 08/17/2008
16:31:29 needed for thread 1
ORA-00289: suggestion :
D:\app\Administrator\fast_recovery_area\TEST\ARCHIVELOG \2008_08_17/o1_mf_1_9_4bk9p2mz_.arcORA-00280:
change 5112647 for thread 1 is in sequence #9
Log applied.
Media recovery complete.

8. Oracle will apply the needed redo and then return you to the SQL prompt. Assuming no errors occur, you can now open the database with the alter database open command as shown here:

SQL> alter database open resetlogs;
Database altered.



Friday, November 15, 2013

ORA-1031 with password file authentication

Troubleshooting ORA-1031 with password file authentication



If a local or remote sysdba connection fails with ORA-01031 than consider following factors : 

1. The database parameter remote_login_passwordfile has to be set to either EXCLUSIVE or SHARED . 

SQL> ALTER SYSTEM SET REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE SCOPE=SPFILE;
restart the database for the change to take effect. 

2. A password file is created in $ORACLE_HOME/dbs with option " nosysdba=n " . In general the name of the file would be in the format orapw<SID> .

In case of uncertainity recreate the password file using the below syntax : 


$ > orapwd file=$ORACLE_HOME/dbs/orapw<sid> password=<password> force=y nosysdba=n
 restart the database . 

The path to the password file %ORACLE_HOME%\database\PWD%ORACLE_SID%.ORA on a Microsoft Windows machine.



Wednesday, November 13, 2013

Default Oracle Passwords

Just a few default Oracle usernames and associated passwords to go with them:

(Note:-  You will need to place this file in the OAT/ OScanner directories as the default installation of these tools only checks for around 130 of the 600 quoted here).

_________________________________________________
#INTERNAL
ORACLE
#INTERNAL
SYS_STNT
ABM
ABM
ADAMS
WOOD
ADLDEMO
ADLDEMO
ADMIN
JETSPEED
ADMIN
WELCOME
ADMINISTRATOR
ADMIN
ADMINISTRATOR
ADMINISTRATOR
AHL
AHL
AHM
AHM
AK
AK
ALHRO
XXX
ALHRW
XXX
ALR
ALR
AMS
AMS
AMV
AMV
ANDY
SWORDFISH
ANONYMOUS
ANONYMOUS
ANONYMOUS
<INVALID>
AP
AP
APPLMGR
APPLMGR
APPLSYS
APPLSYS
APPLSYS
APPS
APPLSYS
FND
APPLSYSPUB
APPLSYSPUB
APPLSYSPUB
PUB
APPLSYSPUB
FNDPUB
APPLYSYSPUB
FNDPUB
APPLYSYSPUB
PUB
APPLYSYSPUB
<UNKNOWN>
APPS
APPS
APPS_MRC
APPS
APPUSER
APPPASSWORD
AQ
AQ
AQDEMO
AQDEMO
AQJAVA
AQJAVA
AQUSER
AQUSER
AR
AR
ASF
ASF
ASG
ASG
ASL
ASL
ASO
ASO
ASP
ASP
AST
AST
ATM
SAMPLEATM
AUDIOUSER
AUDIOUSER
AURORA$JIS$UTILITY$
<INVALID>
AURORA$JIS$UTILITY$
INVALID
AURORA$ORB$UNAUTHENTICATED
INVALID
AURORA$ORB$UNAUTHENTICATED
<INVALID>
AX
AX
AZ
AZ
BC4J
BC4J
BEN
BEN
BIC
BIC
BIL
BIL
BIM
BIM
BIS
BIS
BIV
BIV
BIX
BIX
BLAKE
PAPER
BLEWIS
BLEWIS
BOM
BOM
BRIO_ADMIN
BRIO_ADMIN
BRUGERNAVN
ADGANGSKODE
BRUKERNAVN
PASSWORD
BSC
BSC
BUG_REPORTS
BUG_REPORTS
CALVIN
HOBBES
CATALOG
CATALOG
CCT
CCT
CDEMO82
CDEMO82
CDEMO82
CDEMO83
CDEMO82
UNKNOWN
CDEMOCOR
CDEMOCOR
CDEMORID
CDEMORID
CDEMOUCB
CDEMOUCB
CDOUGLAS
CDOUGLAS
CE
CE
CENTRA
CENTRA
CENTRAL
CENTRAL
CIDS
CIDS
CIS
CIS
CIS
ZWERG
CISINFO
CISINFO
CISINFO
ZWERG
CLARK
CLOTH
CLKANA
<UNKNOWN>
CLKRT
<UNKNOWN>
CN
CN
COMPANY
COMPANY
COMPIERE
COMPIERE
CQSCHEMAUSER
PASSWORD
CQUSERDBUSER
PASSWORD
CRP
CRP
CS
CS
CSC
CSC
CSD
CSD
CSE
CSE
CSF
CSF
CSI
CSI
CSL
CSL
CSMIG
CSMIG
CSP
CSP
CSR
CSR
CSS
CSS
CTXDEMO
CTXDEMO
CTXSYS
<UNKNOWN>
CTXSYS
CHANGE_ON_INSTALL
CTXSYS
CTXSYS
CTXSYS
UNKNOWN
CUA
CUA
CUE
CUE
CUF
CUF
CUG
CUG
CUI
CUI
CUN
CUN
CUP
CUP
CUS
CUS
CZ
CZ
DATA_SCHEMA
LASKJDF098KSDAF09
DBI
MUMBLEFRATZ
DBSNMP
DBSNMP
DBVISION
DBVISION
DCM
<UNKNOWN>
DDIC
199220706
DEMO
DEMO
DEMO8
DEMO8
DEMO9
DEMO9
DES
DES
DES2K
DES2K
DEV2000_DEMOS
DEV2000_DEMOS
DIANE
PASSWO1
DIP
DIP
DISCOVERER_ADMIN
DISCOVERER_ADMIN
DISCOVERER5
<UNKNOWN>
DMSYS
DMSYS
DPF
DPFPASS
DSGATEWAY
<UNKNOWN>
DSGATEWAY
DSGATEWAY
DSSYS
DSSYS
DTSP
DTSP
EAA
EAA
EAM
EAM
EARLYWATCH
SUPPORT
EAST
EAST
EC
EC
ECX
ECX
EJB
EJB
EJSADMIN
EJSADMIN
EJSADMIN
EJSADMIN_PASSWORD
EMP
EMP
ENG
ENG
ENI
ENI
ESTOREUSER
ESTORE
EVENT
EVENT
EVM
EVM
EXAMPLE
EXAMPLE
EXFSYS
EXFSYS
EXTDEMO
EXTDEMO
EXTDEMO2
EXTDEMO2
FA
FA
FEM
FEM
FII
FII
FINANCE
FINANCE
FINPROD
FINPROD
FLM
FLM
FND
FND
FOO
BAR
FPT
FPT
FRM
FRM
FROSTY
SNOWMAN
FTE
FTE
FV
FV
GL
GL
GMA
GMA
GMD
GMD
GME
GME
GMF
GMF
GMI
GMI
GML
GML
GMP
GMP
GMS
GMS
GPFD
GPFD
GPLD
GPLD
GR
GR
HADES
HADES
HCPARK
HCPARK
HLW
HLW
HR
<UNKNOWN>
HR
CHANGE_ON_INSTALL
HR
HR
HR
UNKNOWN
HRI
HRI
HVST
HVST
HXC
HXC
HXT
HXT
IBA
IBA
IBE
IBE
IBP
IBP
IBU
IBU
IBY
IBY
ICDBOWN
ICDBOWN
ICX
ICX
IDEMO_USER
IDEMO_USER
IEB
IEB
IEC
IEC
IEM
IEM
IEO
IEO
IES
IES
IEU
IEU
IEX
IEX
IFSSYS
IFSSYS
IGC
IGC
IGF
IGF
IGI
IGI
IGS
IGS
IGW
IGW
IMAGEUSER
IMAGEUSER
IMC
IMC
IMEDIA
IMEDIA
IMT
IMT
INTERNAL
ORACLE
INTERNAL
SYS_STNT
INV
INV
IPA
IPA
IPD
IPD
IPLANET
IPLANET
ISC
ISC
ITG
ITG
JA
JA
JAKE
PASSWO4
JE
JE
JG
JG
JILL
PASSWO2
JL 
JL 
JMUSER
JMUSER
JOHN
JOHN
JONES
STEEL
JTF
JTF
JTM
JTM
JTS
JTS
JWARD
AIROPLANE
KWALKER
KWALKER
L2LDEMO
L2LDEMO
LBACSYS
LBACSYS
LIBRARIAN
SHELVES
MANPROD
MANPROD
MARK
PASSWO3
MASCARM
MANAGER
MASTER
PASSWORD
MDDATA
MDDATA
MDDEMO
MDDEMO
MDDEMO_CLERK
CLERK
MDDEMO_CLERK
MGR
MDDEMO_MGR
MDDEMO_MGR
MDDEMO_MGR
MGR
MDSYS
MDSYS
ME
ME
MFG
MFG
MGR
MGR
MGWUSER
MGWUSER
MIGRATE
MIGRATE
MILLER
MILLER
MMO2
MMO2
MMO2
MMO3
MMO2
UNKNOWN
MODTEST
YES
MOREAU
MOREAU
MRP
MRP
MSC
MSC
MSD
MSD
MSO
MSO
MSR
MSR
MTS_USER
MTS_PASSWORD
MTSSYS
MTSSYS
MWA
MWA
MXAGENT
MXAGENT
NAMES
NAMES
NEOTIX_SYS
NEOTIX_SYS
NNEUL
NNEULPASS
NOM_UTILISATEUR
MOT_DE_PASSE
NOME_UTILIZADOR
SENHA
NOMEUTENTE
PASSWORD
NUME_UTILIZATOR
PAROL
OAIHUB902
<UNKNOWN>
OAS_PUBLIC
OAS_PUBLIC
OAS_PUBLIC
<UNKNOWN>
OCITEST
OCITEST
OCM_DB_ADMIN
<UNKNOWN>
OCM_DB_ADMIN
OCM_DB_ADMIN
ODM
ODM
ODM_MTR
MTRPW
ODS
ODS
ODS_SERVER
ODS_SERVER
ODSCOMMON
ODSCOMMON
OE
CHANGE_ON_INSTALL
OE
UNKNOWN
OE
OE
OEM_REPOSITORY
<UNKNOWN>
OEMADM
OEMADM
OEMREP
OEMREP
OKB
OKB
OKC
OKC
OKE
OKE
OKI
OKI
OKO
OKO
OKR
OKR
OKS
OKS
OKX
OKX
OLAPDBA
OLAPDBA
OLAPSVR
INSTANCE
OLAPSVR
OLAPSVR
OLAPSYS
MANAGER
OLAPSYS
OLAPSYS
OMWB_EMULATION
ORACLE
ONT
ONT
OO
OO
OPENSPIRIT
OPENSPIRIT
OPI
OPI
ORACACHE
<UNKNOWN>
ORACACHE
ORACACHE
ORACLE
ORACLE
ORADBA
ORADBAPASS
ORANGE
<UNKNOWN>
ORAPROBE
ORAPROBE
ORAREGSYS
ORAREGSYS
ORASSO
ORASSO
ORASSO_DS
ORASSO_DS
ORASSO_PA
ORASSO_PA
ORASSO_PS
ORASSO_PS
ORASSO_PUBLIC
ORASSO_PUBLIC
ORASTAT
ORASTAT
ORCLADMIN
WELCOME
ORDCOMMON
ORDCOMMON
ORDPLUGINS
ORDPLUGINS
ORDSYS
ORDSYS
OSE$HTTP$ADMIN
Invalid password
OSE$HTTP$ADMIN
INVALID
OSM
OSM
OSP22
OSP22
OSSAQ_HOST
<UNKNOWN>
OSSAQ_PUB
<UNKNOWN>
OSSAQ_SUB
<UNKNOWN>
OTA
OTA
OUTLN
OUTLN
OWA
OWA
OWA_PUBLIC
OWA_PUBLIC
OWF_MGR
<UNKNOWN>
OWF_MGR
OWF_MGR
OWNER
OWNER
OZF
OZF
OZP
OZP
OZS
OZS
PA
PA
PANAMA
PANAMA
PATROL
PATROL
PAUL
PAUL
PERFSTAT
PERFSTAT
PERSTAT
PERSTAT
PJM
PJM
PLANNING
PLANNING
PLEX
PLEX
PLSQL
SUPERSECRET
PM
CHANGE_ON_INSTALL
PM
UNKNOWN
PM
PM
PMI
PMI
PN
PN
PO
PO
PO7
PO7
PO8
PO8
POA
POA
POM
POM
PORTAL
<UNKNOWN>
PORTAL_APP
<UNKNOWN>
PORTAL_DEMO
<UNKNOWN>
PORTAL_DEMO
PORTAL_DEMO
PORTAL_PUBLIC
<UNKNOWN>
PORTAL_SSO_PS
PORTAL_SSO_PS
PORTAL30
PORTAL30
PORTAL30
PORTAL31
PORTAL30_ADMIN
PORTAL30_ADMIN
PORTAL30_DEMO
PORTAL30_DEMO
PORTAL30_PS
PORTAL30_PS
PORTAL30_PUBLIC
PORTAL30_PUBLIC
PORTAL30_SSO
PORTAL30_SSO
PORTAL30_SSO_ADMIN
PORTAL30_SSO_ADMIN
PORTAL30_SSO_PS
PORTAL30_SSO_PS
PORTAL30_SSO_PUBLIC
PORTAL30_SSO_PUBLIC
POS
POS
POWERCARTUSER
POWERCARTUSER
PRIMARY
PRIMARY
PSA
PSA
PSB
PSB
PSP
PSP
PUBSUB
PUBSUB
PUBSUB1
PUBSUB1
PV
PV
QA
QA
QDBA
QDBA
QP
QP
QS
CHANGE_ON_INSTALL
QS
QS
QS
UNKNOWN
QS_ADM
CHANGE_ON_INSTALL
QS_ADM
QS_ADM
QS_ADM
UNKNOWN
QS_CB
CHANGE_ON_INSTALL
QS_CB
QS_CB
QS_CB
UNKNOWN
QS_CBADM
CHANGE_ON_INSTALL
QS_CBADM
QS_CBADM
QS_CBADM
UNKNOWN
QS_CS
CHANGE_ON_INSTALL
QS_CS
QS_CS
QS_CS
UNKNOWN
QS_ES
CHANGE_ON_INSTALL
QS_ES
QS_ES
QS_ES
UNKNOWN
QS_OS
CHANGE_ON_INSTALL
QS_OS
QS_OS
QS_OS
UNKNOWN
QS_WS
CHANGE_ON_INSTALL
QS_WS
QS_WS
QS_WS
UNKNOWN
RE
RE
REP_MANAGER
DEMO
REP_OWNER
DEMO
REP_OWNER
REP_OWNER
REP_USER
DEMO
REPADMIN
REPADMIN
REPORTS
REPORTS
REPORTS_USER
OEM_TEMP
RG
RG
RHX
RHX
RLA
RLA
RLM
RLM
RMAIL
RMAIL
RMAN
RMAN
RRS
RRS
SAMPLE
SAMPLE
SAP
SAPR3
SAP
6071992
SAPR3
SAP
SCOTT
TIGER
SCOTT
TIGGER
SDOS_ICSAP
SDOS_ICSAP
SECDEMO
SECDEMO
SERVICECONSUMER1
SERVICECONSUMER1
SH
CHANGE_ON_INSTALL
SH
SH
SH
UNKNOWN
SI_INFORMTN_SCHEMA
SI_INFORMTN_SCHEMA
SITEMINDER
SITEMINDER
SLIDE
SLIDEPW
SPIERSON
SPIERSON
SSP
SSP
STARTER
STARTER
STRAT_USER
STRAT_PASSWD
SWPRO
SWPRO
SWUSER
SWUSER
SYMPA
SYMPA
SYS
0RACLE8
SYS
0RACLE9
SYS
0RACLE8I
SYS
0RACL38
SYS
0RACL39
SYS
0RACL38I
SYS
CHANGE_ON_INSTALL
SYS
D_SYSPW
SYS
MANAGER
SYS
ORACLE
SYS
SYS
SYS
SYSPASS
SYS
MANAG3R
SYS
ORACL3
SYS
0RACLE
SYS
0RACL3
SYS
ORACLE8
SYS
ORACLE9
SYS
ORACLE8I
SYS
ORACLE9I
SYS
0RACLE9I
SYS
0RACL39I
SYSADM
SYSADM
SYSADMIN
<UNKNOWN>
SYSADMIN
SYSADMIN
SYSMAN
SYSMAN
SYSMAN
OEM_TEMP
SYSTEM
CHANGE_ON_INSTALL
SYSTEM
D_SYSPW
SYSTEM
MANAGER
SYSTEM
ORACLE
SYSTEM
SYSTEMPASS
SYSTEM
SYSTEM
SYSTEM
MANAG3R
SYSTEM
ORACL3
SYSTEM
0RACLE
SYSTEM
0RACL3
SYSTEM
ORACLE8
SYSTEM
ORACLE9
SYSTEM
ORACLE9I
SYSTEM
0RACLE9I
SYSTEM
0RACL39I
SYSTEM
D_SYSTPW
SYSTEM
ORACLE8I
SYSTEM
0RACLE8
SYSTEM
0RACLE9
SYSTEM
0RACLE8I
SYSTEM
0RACL38
SYSTEM
0RACL39
SYSTEM
0RACL38I
TAHITI
TAHITI
TALBOT
MT6CH5
TDOS_ICSAP
TDOS_ICSAP
TEC
TECTEC
TEST
PASSWD
TEST
TEST
TEST_USER
TEST_USER
TESTPILOT
TESTPILOT
THINSAMPLE
THINSAMPLEPW
TIBCO
TIBCO
TIP37
TIP37
TRACESVR
TRACE
TRAVEL
TRAVEL
TSDEV
TSDEV
TSUSER
TSUSER
TURBINE
TURBINE
UDDISYS
<UNKNOWN>
ULTIMATE
ULTIMATE
UM_ADMIN
UM_ADMIN
UM_CLIENT
UM_CLIENT
USER
USER
USER_NAME
PASSWORD
USER0
USER0
USER1
USER1
USER2
USER2
USER3
USER3
USER4
USER4
USER5
USER5
USER6
USER6
USER7
USER7
USER8
USER8
USER9
USER9
USUARIO
CLAVE
UTILITY
UTILITY
UTLBSTATU
UTLESTAT
VEA
VEA
VEH
VEH
VERTEX_LOGIN
VERTEX_LOGIN
VIDEOUSER
VIDEOUSER
VIF_DEVELOPER
VIF_DEV_PWD
VIRUSER
VIRUSER
VPD_ADMIN
AKF7D98S2
VRR1
VRR1
VRR1
VRR2
VRR1
UNKNOWN
WEBCAL01
WEBCAL01
WEBDB
WEBDB
WEBREAD
WEBREAD
WEBSYS
MANAGER
WEBUSER
YOUR_PASS
WEST
WEST
WFADMIN
WFADMIN
WH
WH
WIP
WIP
WIRELESS
<UNKNOWN>
WK_PROXY
<UNKNOWN>
WK_SYS
<UNKNOWN>
WK_TEST
WK_TEST
WKADMIN
WKADMIN
WKPROXY
WKPROXY
WKPROXY
CHANGE_ON_INSTALL
WKPROXY
UNKNOWN
WKSYS
CHANGE_ON_INSTALL
WKSYS
WKSYS
WKUSER
WKUSER
WMS
WMS
WMSYS
WMSYS
WOB
WOB
WPS
WPS
WSH
WSH
WSM
WSM
WWW
WWW
WWWUSER
WWWUSER
XADEMO
XADEMO
XDB
CHANGE_ON_INSTALL
XDP
XDP
XLA
XLA
XNC
XNC
XNI
XNI
XNM
XNM
XNP
XNP
XNS
XNS
XPRT
XPRT
XTR
XTR