1. On the database server, using the unix prompt logged in as oracle: ulimit -a (we are looking for max user processes) ps -eaf|grep LOCAL|wc -l (this will tell us the number of database connection processes) more /etc/sysctl.conf (check the kernel.sem or semaphores)
  2. From sqlplus connected as sys: show parameter sessions (formula is processes*1.1 eg, 500*1.1=550) show parameter processes (number of OS processes allowed +5 for background processes)
  3. Make sure that the database listener does not have the “queuesize” set.

During the configuration of Oracle Forms & Reports (running config.bat), if the step “Creating reports tools components” fails, check the following:

  1. Open up Control Panel –> Administrative Tools –> Services
  2. Check for the service Windows Management Instrumentation (WMI)
  3. If the service is running, you will need to turn off the Windows service for the rest of the installation.
  4. You may be prompted that it will turn off a couple other services. Click OK.
  5. You will need to deinstall the Oracle Forms configuration (along with deleting the asinst_1 and user_projects folders).
  6. Restart the Forms & Reports configuration (config.bat)

How to configure database tables so that primary keys are automatically generated:

The following example would create an automatic primary key generation with the following table:

  1. Create Table with primary key and any additional attributes.
    create table test (id number, testdata varchar2(255));
  2. Create Sequence
    create sequence test_seq
    start with 1
    increment by 1
  3. Create Trigger
    create trigger test_trigger
    before insert on test
    for each row
    select test_seq.nextval into :new.id from dual;
  4. Test
    insert into test values(‘hello world!’);
    select * from test;

Creates a 5MB Tablespace with autoextend. Substitute “INDX” with the name of the tablespace you desire. The path (as shown below) should be the path leading to your database’s tablespace data files.



1. Locate autorun.exe in directory where PITSS.CON files were originally placed. If you are unable to remember the location, search for “autorun.exe” in Windows Search. NOTE: For Windows Server 2008 or Windows 7, make sure to run autorun.exe as an administrator.

2. Double-click “autorun.exe” to start application


3. Click “Run” on the Security Warning. NOTE: This may or may not appear.


4. Select the version of Oracle Forms that was installed (10g or 11g).


5. Click “Change License”


6. Click “Run” on the Security Warning. NOTE: This may or may not appear.


7. Click “Next” on the “Welcome to PITSS.CON Change License” screen


8. Connect to admin account MIG with password MIG and your database name.




9. Enter the new license key in the spaces provided and click “Change License”. NOTE: If you have the .key file on the PC or server, clicking “Import Key” will automatically fill in the text boxes for you.


10. A screen will appear explaining your license information. When done reading, click “OK”.

11. The new license has successfully been installed. Click “Finish” to finish the license change.


1. Open “PitssCon Web” by clicking on the icon on the desktop or by going to http://[hostname:port]/forms/frmservlet?config=pitsscon.

clip_image016[1] OR clip_image017[1]

2. Log into PITSS.CON using the MIG user.


3. Once logged in, go to “License Administration”.


Once you are in License Administration, if you can see your updated license information, the license key change was successful!


While attempting to change the license key after completing steps 5 & 6, if you receive the error shown below:


You may have selected the incorrect version of Oracle Forms. You will return to the screen shown on step 5 and you can select the version of Oracle Forms which is installed on your computer.

If you try to start or shut down any Weblogic server and you receive the following error:
ASSERTION FAILED: ‘fio_delete(buf)’
In unlock_repository() (src/ext/jfr/c/repository.c:67)
Assertion failed after 0 days, time_elapsed on dayofweek_month_day_year

  1. Go to your %DOMAIN_HOME%\bin folder.
  2. Open the setDomainEnv.cmd using a text editor (Notepad, Wordpad, etc.)
  3. Near the bottom of the file where it says “set JAVA_OPTIONS=%JAVA_OPTIONS%”, add a space and put -XX:-FlightRecorder
    The servers should start or shut down successfully now.

If you try to print reports from Reports Builder and receive the following errors:

  • REP-57054: In-process job terminated: The report generated successfully but distribution to destinations failed.
  • REP-50159: The report generated successfully but distribution to destinations failed.
  • REP-50151: Destination ID name_of_rdf/rep failed with error An error occurred while sending the file to the printer: Name_Of_Printer – Cannot run program “C:\Oracle\Middleware\asinst_1\config\reports\bin\rwlpr”: CreateProcess error=2, The system cannot find the file specified.

The file ‘rwlpr.exe’ might be missing from the C:\Oracle\Middleware\asinst_1\config\reports\bin\rwlpr directory. To fix the problem, you can:

  1. The file ‘rwlpr.exe’ is located in %ORACLE_HOME%\bin.
  2. Copy the file to %ORACLE_INSTANCE%\config\reports\bin.

You should now be able to print from Reports Builder.

If you try to log into PITSS.CON in Windows and you are unable to log in (not being able to go beyond the login screen) despite the fact you entered the correct credentials and the correct database, you should check to see if the TNS Listener is currently running.

1. Test to see if you can ping your database by using the tnsping command in Command Prompt (cmd.exe).


If you receive the message “TNS-12541: TNS:no listener” or anything similar, then your database listener is currently stopped.


2. To turn on your TNS Listener, go to the Control Panel –> Administrative Tools –> Services



3. Locate the TNS Listener associated with your database as shown here. Once you find it, click “Start” where it says “Start the service”. Notice how the word “Started” isn’t currently stated for the TNS Listener.


When the TNS Listener has started, you should see the screen below:


4. Test to see if you can ping your database again using tnsping inside Command Prompt.


As you can see above, we were able to successfully reach the database!

5. You should now be able to log into PITSS.CON. If you reach the main menu after logging in as shown below, the TNS Listener is running and PITSS.CON can communicate with the database.


Depending on user permissions, you might receive possible errors when accessing a Forms application using Webutil such as:
“WUC-19: Unable to write to local file C:\Program Files (x86\Java\jre6\bin\jacob.dll”
If that is the case, it is recommended to dedicate a directory to where users would have the right to download to. After creating the directory, you will need to do the following:

  1. Copy d2kwut60.dll, jacob.dll, and JNIsharedstubs.dll into the directory
  2. On the server where you are accessing the Forms application from, open webutil.cfg in a text editor
  3. Copy the line “#install.syslib.location.client.1=webutil/syslib” and paste it below. HINT: This line is in the middle of the document.
  4. Uncomment the line you pasted
  5. Replace webutil/syslib with the full path to the directory where the 3 dlls will be located in.
  6. Save all changes in webutil.cfg

After that, you should be able to log into your Forms application without a problem.

If none of your WebLogic servers start up automatically (assuming that Node Manager is supposed to automatically start up the servers) and when you try to use nmConnect with your domain name, weblogic username, and weblogic password to try to reconnect the servers, but you receive the following error:

WLSTException: Error occurred while performing nmConnect : Cannot connect to Node Manager. Access to domain ‘FormsDomain’ for user ‘weblogic’ denied

You may need to change the username and password Node Manager uses to connect. You can do this by the following steps:

1. Log into your Administration Console
2. Once logged in, click on the FormsDomain link on the left side of the screen.
3. Go to the Security tab. Make sure to click “Lock & Edit” first!
4. On the bottom, click on “Advanced”.
5. Change the username and password for Node Manager to match what you use to log into your WebLogic servers.
6. Save all changes and then click “Activate Changes”.
7. Shut down all WebLogic servers.
8. Now you should be able to successfully use nmConnect within WLST.

FYI: If any WebLogic server enters a “FAILED_NOT_RESTARTABLE” state during Node Manager testing, you may need to restart your computer/server before proceeding.