Client Easy Oracle 9ir2

 admin  
  1. Oracle 10g Download 64 Bit
  2. Oracle 12c Client Download

PHP Oracle Database Extension. Client Libraries. Oracle Instant Client - a small footprint set of libraries that allows applications and tools to connect to an.

Hi Tom: when I tried to connect to oracle 9.2.0.1.0 from C: orant BIN PLUS33W.EXE I got error: PLS-00553, what should I do? I have tried to change the NLSLANG from AMERICANAMERICA.WE8ISO8859P1 to AMERICANAMERICA.WE8MSWIN1252, it still doesn't work.

By the way the oracle 92 database is: uni code. This is pretty urgent, thank you for your help! SQL.Plus: Release 3.3.4.0.0 - Production on Wed Sep 25 18: Copyright (c) Oracle Corporation 1979, 1996.

All rights reserved. Error accessing package DBMSAPPLICATIONINFO ERROR: ORA-06550: line 1, column 40: PLS-00553: character set name is not recognized ORA-06550: line 0, column 0: PL/SQL: Compilation unit analysis terminated Connected to: Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.1.0 - Production ERROR: ORA-06550: line 1, column 29: PLS-00553: character set name is not recognized ORA-06550: line 0, column 0: PL/SQL: Compilation unit analysis terminated and we said. Thank you, Tom. That is very helpful. However, I do have another client 8.0.5.0.0, it can connect to 8.1.7 database, but not 9i, here is the error, it is not tnsnames related because I did use 8i client was able to connect to this 9i database with the same tnsnames.ora entry, plus I was able to use tnsping fine. C: Oracle Ora81 BINtnsping dows TNS Ping Utility for 32-bit Windows: Version 2.3.4.0.0 - Production on 25-SEP-02 19:39:45 Copyright (c) Oracle Corporation 1995.

All rights reserved. Attempting to contact (ADDRESS=(PROTOCOL=TCP)(HOST=ausdfsdpast01)(PORT=1521)) OK (230 msec) SQL.Plus: Release 8.0.5.0.0 - Production on Wed Sep 25 19: (c) Copyright 1998 Oracle Corporation. All rights reserved. Enter user-name: vvvv/vvvv@dowp Connected to: Oracle8i Enterprise Edition Release 8.1.7.3.0 - Production With the Partitioning option JServer Release 8.1.7.3.0 - Production xxxx@DOWP connect xxxx@dows Enter password: ERROR: ORA-12203: TNS:unable to connect to destination.

Followup September 25, 2002 - 9:19 pm UTC 12203, 00000, 'TNS:unable to connect to destination' //.Cause: Invalid TNS address supplied or destination is not listening. // This error can also occur because of underlying network transport // problems. //.Action: Verify that the service name you entered on the command line // was correct. Ensure that the listener is running at the remote node and // that the ADDRESS parameters specified in TNSNAMES.ORA are correct. // Finally, check that all Interchanges needed to make the connection are // up and running. Tnsping doesn't prove that you can connect. Your SID or SERVICE it probably wrong in the tnsnames entry.

Tnsping only shows that 'there be a listener on that port'. It does not show that 'the database you want that listener to hook you up with exists and is up'. Tom, I totall understanding what you are talking about.

However the oracle 8.1.7.0.0 client is able to connect to the same 82 db: dows. C: cd oracle ora817 bin C: Oracle Ora817 binsqlplus xxxx@dows SQL.Plus: Release 8.1.7.0.0 - Production on Wed Sep 25 21: (c) Copyright 2000 Oracle Corporation. All rights reserved. Enter password: Connected to: Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.1.0 - Production in both 8.0.5 and 8.1.7 client tnsnames file are as following: ifile=H: Network Admin tnsnames.ora which H drive is the shared drive I use. Followup September 26, 2002 - 7:24 am UTC first - try it without ifile, ifile is not a documented supported technique.

Second, lets see the tnsnames.ora entry, perhaps you are using some syntax that was new with 8i and not available in 8.0 Also, try it like this: sqlplus 'scott/tiger@(DESCRIPTION=(ADDRESSLIST=(ADDRESS=(PROTOCOL=TCP)(HOST=aria-dev)(PORT=1529)))(CONNECTDATA=(ORACLESID=ora9i)))' where you put the tnsnames.ora entry right in there - and lets see the cut and paste of that from 8i and 80. Xxxx:xxxx connect xxxx/xxxx@(DESCRIPTION=(ADDRESSLIST =(ADDRESS =(PROTOCOL = TCP)(HOST = ausdf sdpast01)(PORT = 1521)))(CONNECTDATA =(SERVER = DEDICATED)(SERVICENAME = DOWS))); Invalid option. Usage: CONNECT AS SYSDBA SYSOPER Tom: I am more confused when I connect use this tnsnames.ora entry through 8.0.5 client, I got above error.But this client is able to connect to other 8i database no problem. Also this 9i database is able to be connected through 8i client. Also if I connect directly by using database aliase, I got following error, I am going to send you with email since I can't paste here. Tom: actually command line sqlplus exeucte plus33.exe,not plus80.exe. I can't show you the plus80.exe error if use command line.

Easy

Followup September 27, 2002 - 2:02 pm UTC I no longer have an 805 instance, but using 817/806 $ setenv TNSADMIM /export/home/oracle9i/network/admin $ sqlplus scott/tiger@ora9i SQL.Plus: Release 8.1.7.0.0 - Production on Fri Sep 27 14: (c) Copyright 2000 Oracle Corporation. All rights reserved. Connected to: Oracle9i Enterprise Edition Release 9.0.1.2.0 - Production With the Partitioning option JServer Release 9.0.1.2.0 - Production scott@ORA9I.WORLD Disconnected from Oracle9i Enterprise Edition Release 9.0.1.2.0 - Production With the Partitioning option JServer Release 9.0.1.2.0 - Production $ dev806 $!sql sqlplus scott/tiger@ora9i SQL.Plus: Release 8.0.6.0.0 - Production on Fri Sep 27 14: (c) Copyright 1999 Oracle Corporation. All rights reserved. Connected to: Oracle9i Enterprise Edition Release 9.0.1.2.0 - Production With the Partitioning option JServer Release 9.0.1.2.0 - Production scott@ORA9I.WORLD it works, i'm not aware of any big issue in this regards, no. We had cloned an Oracle Apps 11.5.7, 8.1.7.4 database on the same box Sun Solaris. The original env.

GOLD, and the new env. Checked the new Apps DEV2, and all worked except the users other than the oracle can not use sqlplus to access the database and got as issued sqlplus: SEGMENTATION FAULT (coredump). The oracle account has no the problem.

The users have had no problem to access the GOLD database from the GOLD env. The stack trace created on the core dump, which was shown the privilege problem on the sqlplus: - $ gdb $ORACLEHOME/bin/sqlplus core GDB is free software and you are welcome to distribute copies of it under certain conditions; type 'show copying' to see the conditions. There is absolutely no warranty for GDB; type 'show warranty' for details.

GDB 4.15.1 (sparc-sun-solaris2.4), Copyright 1995 Free Software Foundation, Inc. /oraclebasedev2/product/8.1.7/bin/sqlplus: Permission denied. Core was generated by `sqlplus'.

Program terminated with signal 11, Segmentation fault. #0 0xff3d04d0 in?? (gdb) (gdb) q I checked: $ ls -l /oraclebasedev2/product/8.1.7/bin/sqlplus -rwxr-x-x 1 oracle dba 842772 Jun 2 03:44 /oraclebasedev2/product/8.1.7/bin/sqlplus The privilege is the same as the GOLD's Why do the users have the 'Permission denied' on the sqlplus? Work Around: 1.

Create a temporary directory on your server. Copy the contents of the Oracle REBMS Server CD to the temporary directory created in step 1. Search the directory structure created in step 1 for the existence of the filename symcjit.dll. Rename each copy of the symcjit.dll to symcjit.old.

Run the setup.exe from the install win32 directory and install Oracle 8.1.x. That should do it. Make sure you don't have a jre installed already and if you do I believe you also have to rename the symcjit.dll as well. Hi, Just to update what I infer from below metalink alert is connectivity from 9.2 to 7.x is officially desupported and not the other way around. ALERT: Connections from Oracle 9.2 to Oracle7 are Not Supported Type: Note Doc ID: 207319.1 My client has many databases on 7.x clients happily connecting to 9.2. See one below. Isd250 svrmgrl Oracle Server Manager Release 2.3.4.0.0 - Production Copyright (c) Oracle Corporation 1994, 1995.

All rights reserved. Oracle7 Server Release 7.3.4.0.1 - Production With the distributed, replication, parallel query and Spatial Data options PL/SQL Release 2.3.4.0.0 - Production SVRMGR quit Server Manager complete. Isd250 sqlplus dbawk/xxxx@tcusmarp2iam alive SQL.Plus: Release 3.3.4.0.1 - Production on Thu Nov 20 08: Copyright (c) Oracle Corporation 1979, 1996. All rights reserved. Connected to: Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.4.0 - Production SQL quit. Tom, Is there a ROT when it comes to upgrading Oracle client software?

For example a 9.0.1 client can be used to connect to databases from 7.x (??) thru 10g. So what's the incentive in upgrading client software? Is it just good practise to keep the client software version and database version in sync? I've got a few applications that currently use 9.0.1 client software to connect to 9ir2 databases.

Everything seems to work just fine. I'm wondering if there is any need for me to think along the lines of upgrading these clients. Thank you for your time. Hi Tom, We recently upgraded the database from 8.1.7.4 to 9.2.0.6.

With the old tnsnames.ora (on the client side), I am able to connect to 9.2.0.6 database from Forms 6.0. But when I add a new entry in the tnsnames.ora manually for connecting to another database (9.2.0.6) it is not allowing. TNSPING80 is working. But sqlplus and Forms are not working. Unfortunately, Net8 config Asst is not in the menu and when I try to do a custom install of that, it fails with the message 'unable to start a service for Net8 client'. How to make oracle accept the manual entry in tnsnames.ora. I have enabled tracelevelclient=4 and I find that the failed entry has an SID=ORCL.

Client Easy Oracle 9ir2

I do not know how is it happening. Thanks and regards. Tom, I am sorry if the question is irrelevent. All of a sudden I am not able to connect to the database. The DB version is 9.2.

The following is the error that I am getting: H: sqlplus userid@db SQL.Plus: Release 9.0.1.3.0 - Production on Tue Jun 21 15: (c) Copyright 2001 Oracle Corporation. All rights reserved. Enter password: ERROR: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist SVR4 Error: 2: No such file or directory If I use TNSPING, the result is as follows: TNSPING db Used TNSNAMES adapter to resolve the alias Attempting to contact (DESCRIPTION = (ADDRESSLIST = (ADDRESS = (PROTOCOL = TCP) (HOST = yuca)(PORT = 1526))) (CONNECTDATA = (SID = db))) OK (40 msec). I am trying to connect over network. Sorry if this should go down as a new thread, it does seem quite relevant to my issue. Have recently upgraded my db to 10.2 from 10.1.

Am using Perl to issue my SQL/PL-SQL. Before upgrading, I used the cpan version of Oracle's DBD; this is now only available from Oracle. Previously, I could bypass a TNS lookup - Perl and Ora are on the same (Windows) box, there's only one db, I simply didn't (and still don't) need a TNS lookup. However, now when I use the same perl script I get a TNS error. DBI connect(','TC'.) failed: ORA-12560: TNS:protocol adapter error (DBD ERROR: OCIServerAttach) at testOra.pl line 5 My connect string in perl (no TNS, get above err, but didn't before upgrading) is $dbh=DBI-connect('dbi:Oracle:'.etc It does connect however when I use $dbh=DBI-connect('dbi:Oracle:host=LocalHost;sid=TC'.etc Can TNS be bypassed with the new DBD? There is no client - I'm right on the server, like connecting from sqlplus with no '@' (at least as far as my understanding of these things goes - I'm a developer/programmer, my non-PL-&SQL knowledge is rudimentary).

It connected before without even having the listener installed never mind running. Perl is a server-side tool as well so there really should be no requirement for the listener, in an environment with only one db installed on that server (as far as my understanding.) Also, I'm in development, there's nothing to upgrade, so when I say 'upgrade' the db, I actually mean completely uninstall Ora then reinstall from the new release, so either way, the client version isn't relevant because the client will have been ditched then reinstalled to the appropriate release. Err, sorry, I don't know, and I don't think I can find out either because I've now discovered that sqlplus doesn't work. 'Oracle SQL.Plus has encountered a problem and needs to close.' I've rebooted, I've tried using sqlplus from DOS and sqlplusw (note 'w') and both give this fluffy Windows error message. (Why o why did I install a product that's only been released in the past month?) It's still ok connecting to the db via my (noddy, test) perl script, but sqlplus is, excuse my french, knacked. If I do a 'properties' on sqlplus.exe the file version says 10.2.0.1.0.

Which isn't what you want to know. The Perl installation is version 5.8.7. Which isn't what you want to know. The perl client version? I'm stumped, sorry. My best guess is that you want to know what version the oci-files/dlls are.?

- the ones that the Perl DBD invokes. Don't know how I can find that out - but the perl DBD (DBD-Oracle in perl language), the modules that enable perl to 'talk to' Oracle, were installed yesterday (via a perl utility, ppm, which automatically gets the latest version) - so they're as up-to-date as they get. And Oracle was installed on Thu so again, bang up to date. Didn't expect any response on a Sat - but thanks! Tom, I just tried to restart Oracle from remote client using sqlplus: SQL connect sys@corp as sysdba Enter password: Connected. SQL select status from v$instance; STATUS - OPEN SQL shutdown immediate; Database closed. Database dismounted.

ORACLE instance shut down. SQL startup nomount ORACLE instance started. ORA-12514: TNS:listener could not resolve SERVICENAME given in connect descript or SQL select status from v$instance; select status from v$instance. ERROR at line 1: ORA-03114: not connected to ORACLE Now I keep getting ORA-12514 as I try to connect to Oracle. What is my problem - I did not change anything in config. I was able to connect to the database as it was running, but after shutdown it is not possible anymore? Followup June 18, 2006 - 12:20 pm UTC $ oerr ora 4, 00000, 'TNS:listener does not currently know of service requested in connect descriptor' //.Cause: The listener received a request to establish a connection to a // database or other service.

The connect descriptor received by the listener // specified a service name for a service (usually a database service) // that either has not yet dynamically registered with the listener or has // not been statically configured for the listener. This may be a temporary // condition such as after the listener has started, but before the database // instance has registered with the listener. //.Action: // - Wait a moment and try to connect a second time. // - Check which services are currently known by the listener by executing: // lsnrctl services // - Check that the SERVICENAME parameter in the connect descriptor of the // net service name used specifies a service known by the listener. // - If an easy connect naming connect identifier was used, check that // the service name specified is a service known by the listener. // - Check for an event in the listener.log file.

You would need to use STATIC registration - the listener.ora file would have to 'statically' know of this instance. So, it is possible to do this remotely, but only if the DBA has set it up to be permitted explicitly.

Oracle 10g Download 64 Bit

5 Stars to Tom, 1 Star to Oracle documentation Thank you Tom for responding on Sunday! I registered the instance statically in the listener.ora by adding: SIDLISTlistener= (SIDLIST= (SIDDESC= (GLOBALDBNAME=.) (SIDNAME=.) (ORACLEHOME=.))) and it worked. I have to say that I find Oracle documentation pretty confusing. The documentation says that since version 8i Oracle uses dynamic service registration and any static registration in the listener.ora file not required. This works until one day (one Sunday) you decide to restart a database (an imprortant prod database) remotely. BTW: Reading the Oracle documentation I did not understand a concept of having multiple database services.

Can you please give us a example of this (and how to configure this in init.ora)) //. A database can be presented as multiple services and a service can be implemented as multiple database instances.

The service name is a string that is the global database name, that is, a name comprising the database name and domain name, entered during installation or database creation. If you are not sure what the global database name is, you can obtain it from the value of the SERVICENAMES parameter in the initialization parameter file.

I need to connect to an Oracle 8i server, but oci8 does not support it by default. The php documentation says as following: Note: If OCI8 uses 9iR2 client libraries, then PHP can connect to Oracle Database 8i, 9iR2, 10g or 11g. If OCI8 uses 10gR2 client libraries, the database can be 9iR2, 10g, 11g or 12c. If OCI8 uses 11g client libraries, the database can be 9iR2, 10g, 11g or 12c. If OCI8 uses 12c client libraries, the database can be 10gR2, 11g or 12c.

How can I setup OCI8 to use 9iR2 client libraries? My current environment is: I'm on a ubuntu server, Oracle 8i version 8.1.7.4.0 I have already installed instantclient libraries(I'm able to connect to oracle 10i and above) I'm using instantclient version 12.1. Also tried with instantclient version 10.2 Could someone help me figuring out what the problem might be and how to solve it?

Oracle 12c Client Download

Any help is really appreciated. Exactly what version of '8i' are you trying to connect to? The requirements for 8.1.5, for example, are rather different than the requirements for 8.1.7.4. Oracle doesn't generally make obsolete versions of products available for download so you can't download the 9.2 client libraries any longer. If you have a support contract, you can log a Metalink support request and Oracle support can get you the old libraries. Of course, those old libraries may require a rather old version of linux.

– Aug 5 '15 at 21:12.