My friend has a doubt and mailed to me .I have also guided him to this forum with the thread id.
I want some one on Oracle 9IAS to clear the same.
Past three days I am strugging a lot to install Oracle 9IAS under Windows NT 4.0(Workstation). If you have any idea about this or if you know any other friends please help me . I don't know the steps to install and how to configure Oracle Database cache, discoverer viewer 3i.
Its very urgent for me pls.
Attitude:Attack every problem with enthusiasam ...as if your survival depends upon it
Thanks a lot for your help. I implemented Oracle 9IAS in Windows NT. I read one of the good thread in metalink.com. If anybody trying to install oracle 9IAS (Ver 126.96.36.199) please go thru this steps
Just I copied from metalink.com and paste it here
Installation Steps for 9IAS (188.8.131.52)
This document is to provide a step by step install procedure for 9IAS 1.0.2
Enterprise option on NT, with 9IAS on one PC and the database on another PC.
Though the experience on one install may differe from another, this document
explains some of the most common problems during a nd Enterprise Edition install
and its components. Many things are described in further detail in the
Install Guide, and the of of course the pre-Install tasks should be followed first.
SCOPE & APPLICATION
Anyone installing 9ias enterprise edition on NT.
Installation Procedures and Potential Problems for 9IAS 1.0.2 on NT
These notes describe the install steps for 9IAS enterprise option and some of the problems
that may occur. These notes are based on two separate NT machines, machine1 (to have
9ias installed on it) and machine2 (the 'origin' database machine.)
1) Check the network setup of BOTH machines. In particular check
a) that the machine's IP address is a DNS one and not a DHCP one. Fire up a dos
box and do ipconfig /all this will give some info on this. If in any doubt
check with the network administrators, and get them to set you up a permanent DNS
name and address BEFORE proceeding to install.
b) that the 'machine' name which is viewable in control panel - network is
exactly the same as the name by which your machine is known to the DNS networking system.
If they are not the same, get the network administrators to change the name by which your
machine is known on DNS to what you have entered locally on your computer.
* An example of what can go wrong if these are different : When you run a
test form or report, say reports, you can do: http://dns_machine_name:80/dev60html/runrep.htm
- and the test page will be picked up OK.
However, look down trhe page at 'Web host' - and the machine's OWN name
is taken instead, e.g. fred.uk.oracle.com.
To cure this, amend the runrep.htm file.
* In the D:\Oracle\806\Net80\Admin\tnsnames.ora file, the reports server
entry is automatically entered for you, but 'fred' is the host name
rather than the dns name - change it !
c) The machine name also should NOT have any spaces in it, e.g. 'nicks computer.' If it
does, change it on the PC *FIRST*, reboot and then request the network people to change
their description of your machine to the new name (if it has a space in.)
d) Check the 'virtual memory' setting in control panel - system. You should up
this to something like 200 Meg on both machines.
2) Check machine2 - ensure origin database e.g. 8i is installed and up and running, in particular:
a) check the services in control panel. You should have an oracleservice running, as
well as an oraclelistener.
b) The 9ias install guide suggests making the SID and service name the same of the origin
database, it's easier to just make sure you do this when installing it.
c) Check the logins are valid, sys/whatever and system/whatever - 9ias install uses these.
- do NOT rely on a user/pwd login string with no db alias - You HAVE to test this with the full
alias specified in the tnsnames.ora file, e.g. sys/my_sys_pwd@my_database because this is
what machine1 will use.
d) You may hit an ora-01925 when logging in as sys/change_on_install. This is bug fixed in 8.1.7.
To cure it edit the init.ora file and set MAX_ENABLED_ROLES to something higher, e.g. 29.
Your init.ora file may well point to $ORACLE_HOME/admin//pfile - this directory
contains the main init.ora file - enter / edit the MAX_ENABLED_ROLES in here.
e) The 9ias install guide suggest you need to configure the tnsnames.ora and listener.ora files
to handle external procedure requests, and to start an extra listener by doing:
lsnrctl start external_procedure_listener
- this is likely to fail with a tns-01151 as it doesn't tell you how to correctly set this up in
the listener.ora file. [NOTE:117145.1] suggests you add the following entries in listener.ora:
After I had added these the listener started up OK.
However this step doesn't seem essential, I have installed 9IAS 1.0.2 ok
without adding this stuff above.
3) Now on machine1, download the two huge zip files (equivalent to CD 1 and 2) of 9ias
to a new install area directory, call it say ias_install.
a) Unzip these 2 files.
b) Click on setup.exe. This starts the Oracle Universal Installer. Note the various
install directories, port numbers ect as you go. Do not fire up ANY OTHER software
while doing this as Shortly afterwads the machine1 will *automatically* reboot!
Enter your administrator login and the installer will start up again automatically
and the install will continue.
c) After a while you will be prompted for disk1. You will have to RE-EXTRACT
zip file number one first before this will continue !
d) You are then prompted for the Origin Database Connection Info.
enter machine1's host (check with ping on machine 2) , port and Service name.
NOTE: the host is ukp13199 NOT ukp131999.uk.oracle.com BUT
the Service name should be fully qualified np816.uk.oracle.com
(the above may be wrong, service should possibly be just np816.)
e) at this point you are prompted with ther portal DAD and schema logins + pwds.
write this down!
f) enter the sys password for the origin database.
g) enter the portal to go user and pwd - write this down!
h) enter the system password of the origin machine.
i) After a while you will be prompted for disk2. You will have to RE-EXTRACT
zip file number two as well before it will proceed...
4) The installer will now merrily install developer, discoverer, portal.
it will fire up the traditional installers of these products to do this.
wait for this to finish. Even if the installer says 100% finished after the
discovered install and appears to do nothing - WAIT as it will finish in time!
5) The installer will then reach the 'configuration tools' section.
First on the list is the oracle database cache install - the wizard
will start up in a separate window.
a) type in the sys password and the NT administrator account pwd in the box below.
b) If you get ora-12545 at this point your original host string entered was
probably wrong. cancel out.
d) web cache config assistant then completes very quickly, and goes to the
oracle portal config assistant. Enter the connect string as, for example
e) accept defaults of portal30 and portal30 for the oracle portal schema and oracle
portal dad. If you had any other install fail then you will need to either
delete the portal30 user and objects on the origin database first, or just
choose a different name, e.g. portal30b
f) accept the default portal30_sso names for the SSO schema and SSO DAD. If created
already in an aborted install as above, choose a different name eg portal30_sso2
g) Now you are prompted to enter tablespaces.
(If you accepted the defaults it may complain that you need 100M in the tablespaces.
The best best is to create your OWN tablespaces. Choose back and create the
tablespaces as below.)
On machine1, the origin DB machine, fire up sql*plus and create two big tablespaces:
create tablespace biggun1 datafile 'D:\somewhere_with_lots_of_space\biggun1.dat'
size 200M reuse autoextend on next 1M MAXSIZE 300M
create tablespace biggun2 datafile 'D:\somewhere_with_lots_of_space\biggun2.dat'
size 200M reuse autoextend on next 1M MAXSIZE 300M
Then back on the IAS machine2, choose biggun1 for the default tablespace,
and biggun2 for the document and logging tablespaces. Click YES to overwrite
existing portal packages.
Make sure you have lots of virtual memory on the origin DB and close all
unneccessary software. At 60% done the DB machine crashed for me, but this
was using only a 100M tablespace and having some software load on it, see below.
This will appear to hang on 22% for a while. Wait for this to complete.
This then goes to 28% for the next part. Wait for this as it can take quite
This then goes to wait at around 60% for a while, then around 80%,
finally waits a bit more on 100% .
* If the database cache config or portal config fails with ora-012514, this may
be because the machine's system and dns names are different.
* If the DB machine crashes, this may hang the installer and nothing you do will
stop the config or get rid of it. In this case reboot the machine, and the
installer will restart. If you can fire up the config assistant then do so,
otherwise you may have to start all over again. If you think the
install has corrupted, then you can follow [NOTE:124353.1] - this details
how to create a clean machine. In addition,
a) the installer puts itself into
c:\winnt\profiles\all users\start menu\programs\startup
- this will cause it to fire up on each reboot. Delete the entry from here.
- this is what causes the installer to fire up automatically on reboot - if
you get this, stop the installer from task manager and delete the entry
b) Also, on step 8 of the webIV note above, there are some IAS specific
variables added in the system environment - after amending PATH you
may have to scroll down to see - delete these as well.
On the database box, you will have to manually drop everything created by the
drop tablespace biggun1 including contents cascade constraints
In addition, you may have to look for tables in all_tables owned by portal30
and delete these as well.
a) actully from sql*plus on the 816 machine itself, you can connect
to the 816 database@full_alias.uk.oracle.com
b) copy the basic 816 entry from this file to the target IAS machine,
and put it in both 806 tnsnames.ora, and the IAS tnsnames.ora.
c) fire up sqlplus from the IAS bin area - try to connect with the same alias.
- if it works, the problem could be that the 'service name' in various parts
of the tnsnames.ora files has been auto configured, eg for a database called
fred, as fred.uk.oracle.com. Change this to fred and save. Do this for
the other tnsnames.ora file in the 806 area as well.
d) bounce the apache listener and stop and start the 816 database for good measure.
'Oracle HTTP Server components' is the default page it goes to if it
cannot find a URL.
Login as the portal administrator to start off to give full ocntrol
- portal30_admin, portal30_admin
It can be a good idea to check the portal config file:
stored in D:\oracle\isuites\portal30\images
To display images, e.g. in an HTML portlet, do
WebDB 3.0 creates the following schemas in the database during installation:
* The config file 'include' to 'xml.conf' is COMMENTED OUT by default in
- make sure you uncomment this line first in the above oracle_apache.conf.
Optionally, you can then add a new alias in the file below for your own xml stuff:
Then in D:\Oracle\iSuites\xdk\admin\xml.conf :
Alias /xmldemo/ "D:\Oracle\isuites\xdk\myxml/"
( then bounce the apache listener.)
However to just run the demos, you dont have to do the above.
Now edit the emp.xsql file in the directory above and change the connection to
your database alias (origin db) e.g. np816.
Now you have to edit the xml connection config file,
D:\Oracle\iSuites\xdk\lib\XSQLConfig.xml file -
- in here, copy one of the sections and paste it in, and edit it to
point to your origin database.
(each time after amending this, you need to bounce the apache listener)
You should now be able to reference the emp.xsql demo file in \demo\emp as above: