ORA-01722: invalid number
Cause: The attempted conversion of a character string to a number failed because the character string was not a valid numeric literal. Only numeric fields or character fields containing numeric data may be used in arithmetic functions or expressions. Only numeric fields may be added to or subtracted from dates.
Action: Check the character strings in the function or expression. Check that they contain only numbers, a sign, a decimal point, and the character "E" or "e" and retry the operation.
Saturday, November 21, 2009
ORA-06550:
ORA-06550: line string, column string:string
Cause: A PL/SQL compilation error has occurred. The numbers given for line and column are the location in the PL/SQL block where the error occurred.
Action: Refer to the following PL/SQL messages for more information about the error.
Cause: A PL/SQL compilation error has occurred. The numbers given for line and column are the location in the PL/SQL block where the error occurred.
Action: Refer to the following PL/SQL messages for more information about the error.
ORA-06512: at line
Error:
ORA-06512: at line
Cause:
This error message indicates the line number in the PLSQL code that the error resulted.
Action:
For example, if you had the following PLSQL code:
declare
v_number number(2);
begin
v_number := 100;
end;
You would receive the error message:
The first line of the error message (ie: ORA-06502) indicates the error that occurred, while the second line of the error message (ie: ORA-06512) indicates that the error occurred at line 4 of the PLSQL code.
ORA-06512: at line
Cause:
This error message indicates the line number in the PLSQL code that the error resulted.
Action:
For example, if you had the following PLSQL code:
declare
v_number number(2);
begin
v_number := 100;
end;
You would receive the error message:
The first line of the error message (ie: ORA-06502) indicates the error that occurred, while the second line of the error message (ie: ORA-06512) indicates that the error occurred at line 4 of the PLSQL code.
Thursday, November 19, 2009
ORA-12154 TNS:could not resolve service name
ORA-12154 TNS:could not resolve service name
ORA-12154 error occurs at the time of logon process to a database. This error indicates that the communication software (TNS) in Oracle ( SQL *Net or Net8 ) did not recognize the host/service name of the database specified in the connection parameters.
For a database name to be recognized, it must be resolved by Oracle Client. To resolve a name, Oracle client uses either a TNSNames.ora, A Directory Server or an Oracle Names Server. This error most likely indicates that the resolution is not working and that there is an error in the TNSNAMES.ORA or SQLNET.ORA. For database connectivity to work your database name has to be entered into the TNSNAMES.ORA at a minimum to make this work. In case you are using a directory or names server, we recommend that you check your sqlnet.ora file.
To fix the ORA 12154 error:
Check that the instance or database name is being typed in correctly. It is sometimes also referred to as the connect string of the database
Check the tns names.ora file to validate that the instance name has been entered correctly. If you are in Unix, validate that there are no control characters at the end of the instance or database name and that all paranthesis around the tns entry are properly terminated
If everything looks good in tnsnames.ora, validate that the domain name entry in sqlnet.ora is not conflicting with the full database name resolution.
If you are unable to find a solution, best practice is to delete and recreate the entry to eliminate any character or control character issues.
If the entry you are looking for in your tnsnames.ora is missing, use the following procedure to add a new entry using the SQL*Net Easy configuration utility.
Start>Programs>Oracle >SQL Net Easy Configuration.
Select the option to Add a new instance alias.
Enter the parameters are required in the forms. If you do not have this information, contact your dba.
Confirm the new entry.
Repeat for as many aliases as needed.
Tip : Most tnsnames issues arise out of multiple oracle homes, incorrect entries made somewhere in the file etc.
1. Try searching the drive to identify how many tnsnames.ora files you have
2. Try renaming the tnsnames.ora file in the oracle home where you are facing the issue and add just the entry you are having an issue with. If it works, you know that the issue is somewhere else in the file.
Tip for DBA's : Use a centralized naming service to avoid most issues with client connectivity and the generation of ORA-12154 errors.
ORA-12154 error occurs at the time of logon process to a database. This error indicates that the communication software (TNS) in Oracle ( SQL *Net or Net8 ) did not recognize the host/service name of the database specified in the connection parameters.
For a database name to be recognized, it must be resolved by Oracle Client. To resolve a name, Oracle client uses either a TNSNames.ora, A Directory Server or an Oracle Names Server. This error most likely indicates that the resolution is not working and that there is an error in the TNSNAMES.ORA or SQLNET.ORA. For database connectivity to work your database name has to be entered into the TNSNAMES.ORA at a minimum to make this work. In case you are using a directory or names server, we recommend that you check your sqlnet.ora file.
To fix the ORA 12154 error:
Check that the instance or database name is being typed in correctly. It is sometimes also referred to as the connect string of the database
Check the tns names.ora file to validate that the instance name has been entered correctly. If you are in Unix, validate that there are no control characters at the end of the instance or database name and that all paranthesis around the tns entry are properly terminated
If everything looks good in tnsnames.ora, validate that the domain name entry in sqlnet.ora is not conflicting with the full database name resolution.
If you are unable to find a solution, best practice is to delete and recreate the entry to eliminate any character or control character issues.
If the entry you are looking for in your tnsnames.ora is missing, use the following procedure to add a new entry using the SQL*Net Easy configuration utility.
Start>Programs>Oracle >SQL Net Easy Configuration.
Select the option to Add a new instance alias.
Enter the parameters are required in the forms. If you do not have this information, contact your dba.
Confirm the new entry.
Repeat for as many aliases as needed.
Tip : Most tnsnames issues arise out of multiple oracle homes, incorrect entries made somewhere in the file etc.
1. Try searching the drive to identify how many tnsnames.ora files you have
2. Try renaming the tnsnames.ora file in the oracle home where you are facing the issue and add just the entry you are having an issue with. If it works, you know that the issue is somewhere else in the file.
Tip for DBA's : Use a centralized naming service to avoid most issues with client connectivity and the generation of ORA-12154 errors.
Rapid Clone adcfgclone.pl Error
$ perl adcfgclone.pl appsTier oracle/crpappl/admin/ORACLE_APPSTIER.xml
Enter the APPS password [APPS]:
Running Rapid Clone with command:
perl oracle/crpcomn/clone/bin/adclone.pl java=oracle/crpcomn/clone/bin/../jre/1.3.1
mode=apply stage=oracle/crpcomn/clone/bin/.. component=appsTier
method=CUSTOM appctxtg=oracle/crpappl/admin/ORACLE_APPSTIER.xml
showProgress contextValidated=false
Beginning application tier Apply - Tue Apr 21 03:03:17 2009
Log file located at oracle/crpappl/admin/ORACLE_APPSTIER/log/ApplyAppsTier_04210303.log
RC-50004: Fatal: Error occurred in ApplyAppsTechStack:
Cannot proceed with ApplyAppsTechStack-the paths/ports in the context file are not valid
ERROR while running Apply...
ERROR: Failed to execute oracle/crpcomn/clone/bin/adclone.pl
Enter the APPS password [APPS]:
Running Rapid Clone with command:
perl oracle/crpcomn/clone/bin/adclone.pl java=oracle/crpcomn/clone/bin/../jre/1.3.1
mode=apply stage=oracle/crpcomn/clone/bin/.. component=appsTier
method=CUSTOM appctxtg=oracle/crpappl/admin/ORACLE_APPSTIER.xml
showProgress contextValidated=false
Beginning application tier Apply - Tue Apr 21 03:03:17 2009
Log file located at oracle/crpappl/admin/ORACLE_APPSTIER/log/ApplyAppsTier_04210303.log
RC-50004: Fatal: Error occurred in ApplyAppsTechStack:
Cannot proceed with ApplyAppsTechStack-the paths/ports in the context file are not valid
ERROR while running Apply...
ERROR: Failed to execute oracle/crpcomn/clone/bin/adclone.pl
REP-3000: Internal error starting Oracle Toolkit
REP-3000: Internal error starting Oracle Toolkit
Metalink Note 279342.1
Fix
================
Set the following variables in the reports.sh file (which resides in
the $ORACLE_HOME/bin directory):
REPORTS_DEFAULT_DISPLAY = NO
LDR_CNTRL=MAXDATA = 0x80000000
DISPLAY =
Metalink Note 279342.1
Fix
================
Set the following variables in the reports.sh file (which resides in
the $ORACLE_HOME/bin directory):
REPORTS_DEFAULT_DISPLAY = NO
LDR_CNTRL=MAXDATA = 0x80000000
DISPLAY =
Dblink Details
SELECT dl.owner
,dl.db_link
,dl.username login_name
,dl.host
,to_char(dl.created,'YYMMDD HH24:MI') crdate
FROM dba_db_links dl
ORDER BY dl.owner
,dl.db_link
,dl.db_link
,dl.username login_name
,dl.host
,to_char(dl.created,'YYMMDD HH24:MI') crdate
FROM dba_db_links dl
ORDER BY dl.owner
,dl.db_link
Subscribe to:
Posts (Atom)