EXP-00056: ORACLE error 12541 encountered
ORA-12541: TNS:no listener
EXP-00000: Export terminated unsuccessfully
check your tnsname.ora or your server listener
Showing posts with label Ora Error. Show all posts
Showing posts with label Ora Error. Show all posts
Wednesday, May 14, 2008
Sunday, May 4, 2008
ORA-01034: ORACLE not available
ORA-01034: ORACLE not available
Cause: oracle database/ instance not started
Action: start oracle oracle database/instance
To start oracle simply just logon using sqlplus on local server
sqlplus "/ as sysdba"
then start the database using the following command
sqplus> startup
Cause: oracle database/ instance not started
Action: start oracle oracle database/instance
To start oracle simply just logon using sqlplus on local server
sqlplus "/ as sysdba"
then start the database using the following command
sqplus> startup
Labels:
Ora Error
ORA-00942 : table or view does not exist
ORA-00942: table or view does not exist
Cause: The table or view entered does not exist or you don't have the privilege to that referencestable or view. Or those specified table or view belong to difference schema.
Action: check if you specified the correct table name or check if you have the privilege to the specific object or specified schema and dot in front of those table or view i.e. [schema name].table/view name.
related website
http://www.adp-gmbh.ch/ora/err/ora_00942.html
http://ora-00942.ora-code.com/
.
Cause: The table or view entered does not exist or you don't have the privilege to that referencestable or view. Or those specified table or view belong to difference schema.
Action: check if you specified the correct table name or check if you have the privilege to the specific object or specified schema and dot in front of those table or view i.e. [schema name].table/view name.
related website
http://www.adp-gmbh.ch/ora/err/ora_00942.html
http://ora-00942.ora-code.com/
.
Labels:
Ora Error
ORA-09933 Deletion of old password file failed
ORA-09933: Deletion of old password file failed.
Cause: The removal of the old password file failed or ORACLE was unable to create a password file.
Action: Check the UNIX error number for the specific reason.
Cause: The removal of the old password file failed or ORACLE was unable to create a password file.
Action: Check the UNIX error number for the specific reason.
Labels:
Ora Error
Saturday, May 3, 2008
EXP-00056: ORACLE error 19206 encountered during an expor
EXP-00056: ORACLE error 19206 encountered during an export
Cause: missing or invalid of metadata tables or XMLDB schema was dropped or modified
Action: run the "$ORACLE_HOME/rdbms/admin/catmeta.sql" script when connected as sysdba
you might following error during doing an export of an entire schema in Oracle 9i/10g:
EXP-00056: ORACLE error 19206 encountered
ORA-19206: Invalid value for query or REF CURSOR parameter
ORA-06512: at "SYS.DBMS_XMLGEN", line 83
ORA-06512: at "SYS.DBMS_METADATA", line 353
ORA-06512: at "SYS.DBMS_METADATA", line 418
ORA-06512: at "SYS.DBMS_METADATA", line 457
ORA-06512: at "SYS.DBMS_METADATA", line 1181
ORA-06512: at "SYS.DBMS_METADATA", line 1162
ORA-06512: at line 1
EXP-00056: ORACLE error 19206 encountered
ORA-19206: Invalid value for query or REF CURSOR parameter
ORA-06512: at "SYS.DBMS_XMLGEN", line 83
ORA-06512: at "SYS.DBMS_METADATA", line 353
ORA-06512: at "SYS.DBMS_METADATA", line 418
ORA-06512: at "SYS.DBMS_METADATA", line 457
ORA-06512: at "SYS.DBMS_METADATA", line 1181
ORA-06512: at "SYS.DBMS_METADATA", line 1162
ORA-06512: at line 1
EXP-00000: Export terminated unsuccessfully
(END)
if you do a a single table export could do the trick, but exporting an entire user ("schema") failed with the above error.
This cause of this EXP-00056: ORACLE error 19206 might either be the missing or invalid of metadata tables which need for performing an export or you have dropped or modified the XMLDB schema.
The solution is simply run the following script when connected as sysdba:
$ORACLE_HOME/rdbms/admin/catmeta.sql
i.e. login to your oracle database
at the command line prompt enter
sqlplus "/ as sysdba"
at the sqlplus prompt enter
sqlplus>@$ORACLE_HOME/rdbms/admin/catmeta.sql
Cause: missing or invalid of metadata tables or XMLDB schema was dropped or modified
Action: run the "$ORACLE_HOME/rdbms/admin/catmeta.sql" script when connected as sysdba
you might following error during doing an export of an entire schema in Oracle 9i/10g:
EXP-00056: ORACLE error 19206 encountered
ORA-19206: Invalid value for query or REF CURSOR parameter
ORA-06512: at "SYS.DBMS_XMLGEN", line 83
ORA-06512: at "SYS.DBMS_METADATA", line 353
ORA-06512: at "SYS.DBMS_METADATA", line 418
ORA-06512: at "SYS.DBMS_METADATA", line 457
ORA-06512: at "SYS.DBMS_METADATA", line 1181
ORA-06512: at "SYS.DBMS_METADATA", line 1162
ORA-06512: at line 1
EXP-00056: ORACLE error 19206 encountered
ORA-19206: Invalid value for query or REF CURSOR parameter
ORA-06512: at "SYS.DBMS_XMLGEN", line 83
ORA-06512: at "SYS.DBMS_METADATA", line 353
ORA-06512: at "SYS.DBMS_METADATA", line 418
ORA-06512: at "SYS.DBMS_METADATA", line 457
ORA-06512: at "SYS.DBMS_METADATA", line 1181
ORA-06512: at "SYS.DBMS_METADATA", line 1162
ORA-06512: at line 1
EXP-00000: Export terminated unsuccessfully
(END)
if you do a a single table export could do the trick, but exporting an entire user ("schema") failed with the above error.
This cause of this EXP-00056: ORACLE error 19206 might either be the missing or invalid of metadata tables which need for performing an export or you have dropped or modified the XMLDB schema.
The solution is simply run the following script when connected as sysdba:
$ORACLE_HOME/rdbms/admin/catmeta.sql
i.e. login to your oracle database
at the command line prompt enter
sqlplus "/ as sysdba"
at the sqlplus prompt enter
sqlplus>@$ORACLE_HOME/rdbms/admin/catmeta.sql
Labels:
Ora Error
Friday, May 2, 2008
ORA-06512: at line
For the error message ORA-06512
I had done my search through google and the result came up as below.
As the list below I had saved you sometime. Have a look and see if this could solved your prob if not you can drop me a line or comment I would do more search on it for you, the only thing is I need your error message in more detail.
ORA-06512: at stringline string
Cause: Backtrace message as the stack is unwound by unhandled exceptions.
Action: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or DBA.
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 following 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.
In this example, you've tried to assign a 3 digit number to a variable called v_number that can only handle 2 digits. You could correct this error by redefining the v_number variable as number(3).
declare
v_number number(3);
begin
v_number := 100;
end;
Source: http://www.techonthenet.com/oracle/errors/ora06512.php
ORA-06512 or ORA-6512 is a common error faced by oracle users and administrators alike during the operations of an oracle database. The ORA-06512 error in itself does not indicate the actual issue or an exception code. ORA-06512 normally indicates the line number at which the oracle PL/SQL code has caused an error or exception condition. The rest of the article provides steps to analyze this error along with further references that can be leveraged for solving an error ORA-06512.
Error Description. [Oracle][ODBC][Ora]ORA-01013: user requested cancel of current operation
ORA-06512: at "MMS_TEST.YPPAMERGE", line 93
ORA-06512: at line 1
In the above example, ORA 6512 message generated by the oracle database server indicates that the error 1013 was caused by the user cancelling the current operation while the ORA 06512 error indicates the line number at which the code execution was cancelled.
You should try to focus on the ORA-01013 oracle error in this case and use the ORA 6512 to identify the line number or code which has caused an exception and fix the exception or add an additional exception handler based on the type of error.
ORA-06512 at string line string
Cause: Backtrace message as the stack is unwound by unhandled exceptions.
Action: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or DBA
ORA-06512 Notes :
Q : ORA-6512 and ORA-00600 ..I am running into the following error when I try to export my database in 10g...
exporting pre-schema procedural objects and actions
. exporting cluster definitions
EXP-00056: ORACLE error 600 encountered
ORA-00600 : internal error code, arguments: [qmtInit1],
ORA-06512 : at "SYS.DBMS_METADATA", line 1511
A: You may be running into a known XDB Bug listed at the following documents in Metalink..looks like an xdb bug listed in bug id's 3939845, 2626241, 2730857. Look up in metalink for answers surrounding the same.
source: http://www.mydatabasesupport.com/ora-06512-at-line.html
I had done my search through google and the result came up as below.
As the list below I had saved you sometime. Have a look and see if this could solved your prob if not you can drop me a line or comment I would do more search on it for you, the only thing is I need your error message in more detail.
ORA-06512: at stringline string
Cause: Backtrace message as the stack is unwound by unhandled exceptions.
Action: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or DBA.
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 following 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.
In this example, you've tried to assign a 3 digit number to a variable called v_number that can only handle 2 digits. You could correct this error by redefining the v_number variable as number(3).
declare
v_number number(3);
begin
v_number := 100;
end;
Source: http://www.techonthenet.com/oracle/errors/ora06512.php
ORA-06512 or ORA-6512 is a common error faced by oracle users and administrators alike during the operations of an oracle database. The ORA-06512 error in itself does not indicate the actual issue or an exception code. ORA-06512 normally indicates the line number at which the oracle PL/SQL code has caused an error or exception condition. The rest of the article provides steps to analyze this error along with further references that can be leveraged for solving an error ORA-06512.
Error Description. [Oracle][ODBC][Ora]ORA-01013: user requested cancel of current operation
ORA-06512: at "MMS_TEST.YPPAMERGE", line 93
ORA-06512: at line 1
In the above example, ORA 6512 message generated by the oracle database server indicates that the error 1013 was caused by the user cancelling the current operation while the ORA 06512 error indicates the line number at which the code execution was cancelled.
You should try to focus on the ORA-01013 oracle error in this case and use the ORA 6512 to identify the line number or code which has caused an exception and fix the exception or add an additional exception handler based on the type of error.
ORA-06512 at string line string
Cause: Backtrace message as the stack is unwound by unhandled exceptions.
Action: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or DBA
ORA-06512 Notes :
Q : ORA-6512 and ORA-00600 ..I am running into the following error when I try to export my database in 10g...
exporting pre-schema procedural objects and actions
. exporting cluster definitions
EXP-00056: ORACLE error 600 encountered
ORA-00600 : internal error code, arguments: [qmtInit1],
ORA-06512 : at "SYS.DBMS_METADATA", line 1511
A: You may be running into a known XDB Bug listed at the following documents in Metalink..looks like an xdb bug listed in bug id's 3939845, 2626241, 2730857. Look up in metalink for answers surrounding the same.
source: http://www.mydatabasesupport.com/ora-06512-at-line.html
Labels:
Ora Error
ORA-01422: exact fetch returns more than requested number of rows
ORA-01422: exact fetch returns more than requested number of rows
Cause: The number specified in exact fetch is less than the rows returned.
Action: Rewrite the query or change number of rows requested
With Oralce ORA-01422 error the cause would be you tried to execute a SELECT INTO statement and more than one row was returned. This error is on oracle PL/SQL lanugauge.
Here are the option that you could do.
1. rewrite your sql statement so it return only one record.
2. use an exception in case of unexpected scenario.
The exception syntax would look like this
Syntax:
BEGIN
your sql statement here
ie. select a, b, c into d, e, f from i;
EXCEPTION
WHEN exception1 [OR exception2...]] THEN
...
[WHEN exception3 [OR exception4...] THEN
...]
[WHEN OTHERS THEN
...]
your code need to be something like
BEGIN
your sql statement here
ie. select a, b, c into d, e, f from i;
EXCEPTION
WHEN TOO_MANY_ROWS THEN
do something ie. raise error
WHEN OTHERS THEN
do something
END;
3. use cursor for more information on cursor take a look at
http://www.oracle-base.com/articles/8i/UsingRefCursorsToReturnRecordsets.php.
http://www.psoug.org/reference/ref_cursors.html
Cause: The number specified in exact fetch is less than the rows returned.
Action: Rewrite the query or change number of rows requested
With Oralce ORA-01422 error the cause would be you tried to execute a SELECT INTO statement and more than one row was returned. This error is on oracle PL/SQL lanugauge.
Here are the option that you could do.
1. rewrite your sql statement so it return only one record.
2. use an exception in case of unexpected scenario.
The exception syntax would look like this
Syntax:
BEGIN
your sql statement here
ie. select a, b, c into d, e, f from i;
EXCEPTION
WHEN exception1 [OR exception2...]] THEN
...
[WHEN exception3 [OR exception4...] THEN
...]
[WHEN OTHERS THEN
...]
your code need to be something like
BEGIN
your sql statement here
ie. select a, b, c into d, e, f from i;
EXCEPTION
WHEN TOO_MANY_ROWS THEN
do something ie. raise error
WHEN OTHERS THEN
do something
END;
3. use cursor for more information on cursor take a look at
http://www.oracle-base.com/articles/8i/UsingRefCursorsToReturnRecordsets.php.
http://www.psoug.org/reference/ref_cursors.html
Labels:
Ora Error
ORA-00001: unique constraint (string.string) violated
ORA-00001: unique constraint (string.string) violated
Cause: An UPDATE or INSERT statement attempted to insert a duplicate key. For Trusted Oracle configured in DBMS MAC mode, you may see this message if a duplicate entry exists at a different level.
Action: Either remove the unique restriction or do not insert the key.
the sample message might be as below
insert into student(pk_id, fieldname) values(1, '')
*
ERROR at line 1:
ORA-00001: unique constraint (PROMIS.SYS_C0012876) violated
With the example above we knew that it must be at table student. But if the query is more complex it might be hard to locate the problem constraint. If you already know where the prob is go to step 2 otherwise go to step 1
Step 1.> Locate the problem
To locate where might be the problem you may need to use the following query to find which table is your problem.
select distinct table_name
from all_indexes
where index_name = 'CONSTRAINT_NAME';
replace the CONSTRAINT_NAME with your constraint code (as the example above it is the text with the underline, SYS_C0012876. So the query would be:
select distinct table_name
from all_indexes
where index_name = 'SYS_C0012876';
and you will get the table name which cause the problem.
Step 2.> solve the problem
The options to resolve this Oracle ORA-00001 error are:
1. Modify your SQL so that a duplicate value is not created.
2. Change the constraint to allow duplicate values.
3. Diable the unique constraint.
4. Drop the unique constraint.
from 1-4 I would say it is likely that the first one is quite the right solution for me, as the constraint itself had the reason to be there from the first place. I suggest stick to number 1 to be on the save side, unless you know what you are doing.
Cause: An UPDATE or INSERT statement attempted to insert a duplicate key. For Trusted Oracle configured in DBMS MAC mode, you may see this message if a duplicate entry exists at a different level.
Action: Either remove the unique restriction or do not insert the key.
the sample message might be as below
insert into student(pk_id, fieldname) values(1, '')
*
ERROR at line 1:
ORA-00001: unique constraint (PROMIS.SYS_C0012876) violated
With the example above we knew that it must be at table student. But if the query is more complex it might be hard to locate the problem constraint. If you already know where the prob is go to step 2 otherwise go to step 1
Step 1.> Locate the problem
To locate where might be the problem you may need to use the following query to find which table is your problem.
select distinct table_name
from all_indexes
where index_name = 'CONSTRAINT_NAME';
replace the CONSTRAINT_NAME with your constraint code (as the example above it is the text with the underline, SYS_C0012876. So the query would be:
select distinct table_name
from all_indexes
where index_name = 'SYS_C0012876';
and you will get the table name which cause the problem.
Step 2.> solve the problem
The options to resolve this Oracle ORA-00001 error are:
1. Modify your SQL so that a duplicate value is not created.
2. Change the constraint to allow duplicate values.
3. Diable the unique constraint.
4. Drop the unique constraint.
from 1-4 I would say it is likely that the first one is quite the right solution for me, as the constraint itself had the reason to be there from the first place. I suggest stick to number 1 to be on the save side, unless you know what you are doing.
Labels:
Ora Error
ORA-00936: missing expression
ORA-00936: missing expression
Cause: A required part of a clause or expression has been omitted. For example, a SELECT statement may have been entered without a list of columns or expressions or with an incomplete expression. This message is also issued in cases where a reserved word is misused, as in SELECT TABLE (see case 2 below).
Action: Check the statement syntax and specify the missing component.
1. if you are using prepare statement to connect to oracle with vb or asp you might as get this error as using named parameters. The reason is that OLEDB doesn't support named parameters. e.g.
here i have the example of how to do it
Dim objCmd
Set objCmd = Server.CreateObject("ADODB.Command")
Set objCmd.ActiveConnection = objConn
objCmd.CommandType = adCmdText
objCmd.CommandText = "{CALL procedurename(?,?,?,?,?,?)}"
objCmd.Parameters.Append objCmd.CreateParameter("@a", adVarChar, adParamInput,16)
objCmd.Parameters.Append objCmd.CreateParameter("@b", adVarChar, adParamInput,32)
objCmd.Parameters.Append objCmd.CreateParameter("@c", adDouble, adParamOutput)
objCmd.Parameters.Append objCmd.CreateParameter("@d", adVarChar, adParamOutput,255)
objCmd.Parameters.Append objCmd.CreateParameter("@e", adDouble, adParamOutput)
objCmd.Parameters.Append objCmd.CreateParameter("@f", adDouble, adParamOutput)
objCmd("@a") = sString
objCmd("@b") = sString2
objCmd.Execute
If ERR = 0 Then
o_errnum = objCmd("@c")
o_errStr = objCmd("@d")
o_usertype = objCmd("@e")
o_userid = objCmd("@f")
isValidLogin = True
End If
Set objCmd = Nothing
with this example you can use procedure to pass the paremeter to oracle and at the same time get the output parameters. The keyword is adParamOutput and adParamInput plus you need to specified parameter type make sure they are the same with your oracle procedure. Otherwise you will get an error.
2. If you are not running procedure. The other possibly cause of the error "ORA-00936: missing expression" might be that you tried to execute a SELECT statement and forget to the list of the columns in the SELECT statement.
i.e.
select
from tablename;
this also would raise you the same error
So the solution would be "Check the statement syntax and specify the missing component". If you are calling procedure using ? in your preparestatement not @ as I had already said "OLEDB doesn't support named parameters"
Cause: A required part of a clause or expression has been omitted. For example, a SELECT statement may have been entered without a list of columns or expressions or with an incomplete expression. This message is also issued in cases where a reserved word is misused, as in SELECT TABLE (see case 2 below).
Action: Check the statement syntax and specify the missing component.
1. if you are using prepare statement to connect to oracle with vb or asp you might as get this error as using named parameters. The reason is that OLEDB doesn't support named parameters. e.g.
here i have the example of how to do it
Dim objCmd
Set objCmd = Server.CreateObject("ADODB.Command")
Set objCmd.ActiveConnection = objConn
objCmd.CommandType = adCmdText
objCmd.CommandText = "{CALL procedurename(?,?,?,?,?,?)}"
objCmd.Parameters.Append objCmd.CreateParameter("@a", adVarChar, adParamInput,16)
objCmd.Parameters.Append objCmd.CreateParameter("@b", adVarChar, adParamInput,32)
objCmd.Parameters.Append objCmd.CreateParameter("@c", adDouble, adParamOutput)
objCmd.Parameters.Append objCmd.CreateParameter("@d", adVarChar, adParamOutput,255)
objCmd.Parameters.Append objCmd.CreateParameter("@e", adDouble, adParamOutput)
objCmd.Parameters.Append objCmd.CreateParameter("@f", adDouble, adParamOutput)
objCmd("@a") = sString
objCmd("@b") = sString2
objCmd.Execute
If ERR = 0 Then
o_errnum = objCmd("@c")
o_errStr = objCmd("@d")
o_usertype = objCmd("@e")
o_userid = objCmd("@f")
isValidLogin = True
End If
Set objCmd = Nothing
with this example you can use procedure to pass the paremeter to oracle and at the same time get the output parameters. The keyword is adParamOutput and adParamInput plus you need to specified parameter type make sure they are the same with your oracle procedure. Otherwise you will get an error.
2. If you are not running procedure. The other possibly cause of the error "ORA-00936: missing expression" might be that you tried to execute a SELECT statement and forget to the list of the columns in the SELECT statement.
i.e.
select
from tablename;
this also would raise you the same error
So the solution would be "Check the statement syntax and specify the missing component". If you are calling procedure using ? in your preparestatement not @ as I had already said "OLEDB doesn't support named parameters"
Labels:
Ora Error
EXP-00056: ORACLE error 6550 encountered
EXP-00056: ORACLE error 6550 encountered
ORA-06550: line 1, column 41:
PLS-00302: component 'SET_NO_OUTLINES' must be declared
ORA-06550: line 1, column 15:
PL/SQL: Statement ignored
EXP-00000: Export terminated unsuccessfully
You would get this error when you are trying to export your database with exp binary that is not compatible with your database
the cause of this error is, as the above message had already mention, that you are tring to export your database from client with oracle version higher
than the server version ie. using oracle 10g to export from oracle database 9i.
the solution are
- first option: you need exp program with the same version (or lower one) as your database, which mean
you need to find the client machine with oracle with the same version or lower installed
or
you may need to reinstalled your oracle client.
-second option: if you have an access to your server, physically or remotely, simply just logon and use the exp command from the command line.
Labels:
Ora Error
Wednesday, April 23, 2008
TNS-12535: TNS:operation timed out
There might be sometime that when you try to connect to Oracle Server and you get the error "TNS-12535: TNS:operation timed out". It seem that the server does not exist or the listener does not start or both of them. The first thing you need to have a look is
the tnsnames.ora which could be found at
- $ORACLE_HOME/network/admin for unix like OS ie. every distribute of Linux, Solaris etc.
- ..\oracle\product\10.2.0\ for Windows Platform
in this tnsnames.ora will look like this
ora_service_name =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = ORA_Server)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = ORA_SID)
)
)
there are 2 things you need to have a look there.
The first one is to check if you Ora_SID is correct, if you don't know please contact your dba admin and ask for it.
The Second thing you need to take a look is the HOST part host/ip parth (HOST=....) this is where your oracle server is.
If both Ora_SID and HOST are correct then try to ping the server to see if you can reach the server (there might be the case that the dba admin turn the ping port of for security reason though, in this case you are behind firewall).
To make sure if you are really behind the firewall try telnet the server with this syntax
telnet server_IP 1521 ( or whatever your Oracle listening port is). If you get the following error
Connecting To your server_ipd...Could not open connection to the host, on port 1521:
Connect failed
then 90% you are behind firewall, please contact your network administrator to turn the firewall on port 1521 on.
the tnsnames.ora which could be found at
- $ORACLE_HOME/network/admin for unix like OS ie. every distribute of Linux, Solaris etc.
- ..\oracle\product\10.2.0\ for Windows Platform
in this tnsnames.ora will look like this
ora_service_name =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = ORA_Server)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = ORA_SID)
)
)
there are 2 things you need to have a look there.
The first one is to check if you Ora_SID is correct, if you don't know please contact your dba admin and ask for it.
The Second thing you need to take a look is the HOST part host/ip parth (HOST=....) this is where your oracle server is.
If both Ora_SID and HOST are correct then try to ping the server to see if you can reach the server (there might be the case that the dba admin turn the ping port of for security reason though, in this case you are behind firewall).
To make sure if you are really behind the firewall try telnet the server with this syntax
telnet server_IP 1521 ( or whatever your Oracle listening port is). If you get the following error
Connecting To your server_ipd...Could not open connection to the host, on port 1521:
Connect failed
then 90% you are behind firewall, please contact your network administrator to turn the firewall on port 1521 on.
Labels:
Ora Error
Monday, April 2, 2007
Microsoft OLE DB Provider for ODBC Drivers error '80004005' Specified driver could not be loaded due to system error 5 (Oracle in OraHome92).
Solution Description
--------------------
Oracle 9.2 Client software requires that you give the Authenticated User
privilege to the Oracle Home by following these steps:
1. Log on to Windows as a user with Administrator privileges.
2. Launch Windows Explorer from the Start Menu and and navigate to the
ORACLE_HOME folder. This is typically the "Ora92" folder under the
"Oracle" folder (i.e. D:\Oracle\Ora92).
3. Right-click on the ORACLE_HOME folder and choose the "Properties" option
from the drop down list. A "Properties" window should appear.
4. Click on the "Security" tab of the "Properties" window.
5. Click on "Authenticated Users" item in the "Name" list (on Windows XP
the "Name" list is called "Group or user names").
6. Uncheck the "Read and Execute" box in the "Permissions" list under the
"Allow" column (on Windows XP the "Permissions" list is called
"Permissions for Authenticated Users").
7. Re-check the "Read and Execute" box under the "Allow" column (this is
the box you just unchecked).
8. Click the "Advanced" button and in the "Permission Entries" list make
sure you see the "Authenticated Users" listed there with:
Permission = Read & Execute
Apply To = This folder, subfolders and files
If this is NOT the case, edit that line and make sure the "Apply onto"
drop-down box is set to "This folder, subfolders and files". This
should already be set properly but it is important that you verify this.
9. Click the "Ok" button until you close out all of the security properties
windows. The cursor may present the hour glass for a few seconds as it
applies the permissions you just changed to all subfolders and files.
10. Reboot your computer to assure that these changes have taken effect.
Re-execute the application and it should now work.
ref: http://www.ureader.com/message/451160.aspx
Labels:
Ora Error,
Ora: Error
Wednesday, March 28, 2007
Error: 'ORA-28547: connection to server failed, probable Net8 admin error'
Error: 'ORA-28547: connection to server failed, probable Net8 admin error'
Any other error indicates that the tnsnames.ora, listener.ora, or both are not correct.
Cause: A failure occurred during initialization of a network connection from a client process to the Oracle server:
The connection was completed but a disconnect occurred while trying to perform protocol-specific initialization, usually due to use of different network protocols by opposite sides of the connection.
This usually is caused by incorrect Oracle Net administrative setup for database links or external procedure calls.
The most frequent specific causes are:
* The connection uses a connect string which refers to a Heterogeneous Services agent instead of an Oracle server.
* The connection uses a connect string which includes an (HS=) specification.
Check Oracle Net administration in the following ways:
* When using TNSNAMES.ORA or an Oracle Names server, make sure that the client connection to the ORACLE server uses the correct service name or SID.
* Check LISTENER.ORA on the connection end point's host machine to assure that this service name or SID refers to the correct server.
* Confirm in TNSNAMES.ORA or the equivalent service definition that the connect string does NOT contain (HS=).
Ref: http://www.dbmotive.com/
Any other error indicates that the tnsnames.ora, listener.ora, or both are not correct.
Cause: A failure occurred during initialization of a network connection from a client process to the Oracle server:
The connection was completed but a disconnect occurred while trying to perform protocol-specific initialization, usually due to use of different network protocols by opposite sides of the connection.
This usually is caused by incorrect Oracle Net administrative setup for database links or external procedure calls.
The most frequent specific causes are:
* The connection uses a connect string which refers to a Heterogeneous Services agent instead of an Oracle server.
* The connection uses a connect string which includes an (HS=) specification.
Check Oracle Net administration in the following ways:
* When using TNSNAMES.ORA or an Oracle Names server, make sure that the client connection to the ORACLE server uses the correct service name or SID.
* Check LISTENER.ORA on the connection end point's host machine to assure that this service name or SID refers to the correct server.
* Confirm in TNSNAMES.ORA or the equivalent service definition that the connect string does NOT contain (HS=).
Ref: http://www.dbmotive.com/
Labels:
Ora Error,
ORA-28547,
Ora: Error
Subscribe to:
Posts (Atom)