This content has been marked as final. Show 10 replies
Its probably the Oracle client that installs with Forms 6. Try connecting to the database using SQL Plus from a Forms workstation. If it fails I would install a newer client and switch the Oracle Home on all the workstations.
( Provided it tests out )
I would probably try using the Net Configurations Assistant in your Oracle Start Menu group with all combinations I could think of before I added a second client to the mix.
Of minor interest :
The Windows version might put the hurt on you. This may or may not help that :
Edited by: mseberg on Jun 20, 2012 3:51 PM
Legacy Applications and Oracle 11g
So I'm sorry to say you are out of options. I also checked the Forms Forum and the few posts there on Forms 6 ( Obsolete in 2004 ) all agree. Forms 6 and Oracle 11 database do not play together.
I hope at least I saved you some time.
Edited by: mseberg on Jun 20, 2012 4:36 PM
Upgrading Oracle Forms 6i to Oracle Forms 11g
If I change the set of characters using the following commands, am I going to be able to connect 6i with 11g?
C:\>sqlplus /nolog SQL> connect / as sysdba Conectado. SQL> shutdown immediate SQL> startup restrict SQL> alter database character set internal_use UTF8; SQL> shutdown immediate SQL> startup
As you have already guessed, the key issue is the DB character set. E.g. Forms 6i does not support AL32UTF8.
Changing the character set of an existing database can be a daunting task. Its easier if one can recreate the DB with the required character set. See http://docs.oracle.com/cd/B10500_01/server.920/a96529/ch10.htm
So these steps as they mention on the article that you sent me are the correct to change the character set?
To change the database character set, perform the following steps:
Shut down the database, using either a SHUTDOWN IMMEDIATE or a SHUTDOWN NORMAL statement.
Do a full backup of the database because the ALTER DATABASE CHARACTER SET statement cannot be rolled back.
Complete the following statements:
So the character set that I should use is UTF8 as I mentioned before in the command ALTER DATABASE CHARACTER SET?
STARTUP MOUNT; ALTER SYSTEM ENABLE RESTRICTED SESSION; ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0; ALTER SYSTEM SET AQ_TM_PROCESSES=0; ALTER DATABASE OPEN; ALTER DATABASE CHARACTER SET new_character_set; SHUTDOWN IMMEDIATE; -- or SHUTDOWN NORMAL; STARTUP;
Be careful with the naysayers out there. Forms/Reports 6i client/server (22.214.171.124+) connects just fine to 10.2, 11.1, and 11.2 database so as long as they are not AL32UTF8 character sets. Forms/Reports 6i client/server also works just fine running on a 32bit or 64bit OS while connecting to a 32bit or 64bit Database.
These are the things you have to be careful of:
1) cannot use AL32UTF8 character set, use the default OS character set instead
2) be sure to set the password rules to "legacy", that way forms and reports can work together.
It is not "Supported", but it works just fine.