Hi to All, sorry for English - no Russian keyboard (and Russian driver at all)
So I promised to post this info a few times, now I am ready.
Maybe something is not clearly - feel free to touch me. So:
----------------------------------------------------------
How to install Oracle 9.2.0.1 on SuSe 9.1 PE

I successfully installed Oracle 9.2.0.1 on Suse 9.1 PE. I have pure PC 600 MHz, with 25 GB hard disk. The workflow was the following:

1) Download CD image with SuSe 9.1 from www.suse.com, burn CD
2) Install SuSe 9.1 on PC, during installation skip update
3) Get the document
and read it carefully. Follow the instructions from this document. Of course my installation was a little different.

Pre-installation steps:

1) Download from metalink.oracle.com and apply path #3006854. It allows to prevent bug of running runInstaller.


2) Change shmmax parameter. It prevents ORA-27123 error during database creation


The parameter should be 1073741824. Check it


And reboot the machine

3) At first, check your present glibc


If you can see GLIBC_2.0 you glibc cannot be used for link oemagent. You should rebuild your glibc package. It allows to link oemagent. At first download from rpm.pbone.net last glibc-2.x.x-x.src.rpm


It might the last command was not successful at first time. You should to install a number of packages, which are needed for RPM building. Download and install them from rpm.pbone.net (I used all last for SuSe 9.x) After that try to run the last command again.


And check, your glibc is good right now


4) Install all packages, recommended for Oracle on Suse:
pdksh, gcc_old, libaio, libaio-devel.

5) Install orarun.rmp


This package creates oracle unix account and oinstall, disk (?) group. If you prefer “standard” behavior you should create dba group and oracle account here.

Also this package add “false” shell for oracle. It will be better to create /home/oracle folder and assign it to oracle user, change it shell for bash for example and apply some password.

Installation of oracle:

1) Run runInstaller. Use all settings as you wish except database creation. Skip it.
2) During the linking you will meet 2 errors, related with ins_oemagent.mk and ins_ctx.mk. Ignore it.
3) When the prompt of running root.sh appeared – to do the following


And continue installation. However you ctx error are is fixed yet. You can complete it after installation.

4) The installation should be finished correctly, go to post-installation steps.

Post-installation steps:

1) Fix the error with ctx libraries. It has 2 sub-steps. The first is to apply patch #2037255. The second is to edit env_ctx.mk file. So, download the patch from metalink.oracle.com



2) Now the oracle installation is fine. Add some minor steps. At first make internal runInstaller available


3) Create the database instance
4) Make link in $ORACLE_HOME/dbs folder


5) Edit /etc/oratab file – change “N” to “Y” on your instance name.
6) Edit /etc/sysconfig/oracle file. Change “no” to “yes” against START_ORACLE_DB, START_ORACLE_DB_LISTENER and START_ORACLE_DB_AGENT variables.


ENGOY!

Сходи на сусевый сайт, там есть кой-какая инфа про то как устанавливать на седьмую сусю. А так на первый взгляд наверно можно избежать танцев с бубнами вокруг glibc (как я знаю, glibc-2.3.2-5 экпортит __ctype_ нормально, а не через compat_symbol). Тольки ее уже так просто не найдешь, во-первых, и она так просто не встанет во-вторых. Если "во-первых" еще можно решить (я нашел), то "во-вторых" я думаю пляска очсерьезная. Хотя не пробовал.

2 слава зы

По поводу 9.0.4 (или 9. 2 .0.4?)- не знаю, не пробовал. Мога, быть. Я воще перелапатил много доков, в том числе и по 9.2.0.4, и по 9.0.1. Проблемы везде похожие. Щас буду устанавливать 9.2.0.4. Предыдуший опыт установки _в_лоб_ на сусю выдал где-то 10-12 ошибок на линковке, оракл так и не встал. Примерная картина была и при попытке пропатчевать уже работающий 9.2.0.1 и на 9.2.0.4, и на 9.2.0.5 =(. Воще мне и 9.2.0.3 сойдет, но пока не пробовал. Так что буду разбираться.

По поводу статьи на русском - можно пользвать, для шапки работает. Был один из моих доков, которые я пользовал. Только на сусе orarun.rpm много чего сам делает. Я думаю его и на шапке можно применить, только поддержку Korn Shell поставить, если ее нема.

Today I patched it up to 9.2.0.3
The pathching went fine, however I lost linstener.ora, tnsnames.ora and some others files =(. I do not know, why...
I restored some files manualy and started the listener. However it was impossible to start the agent. Finally I found the following document:
some author
Clean Start Steps:
1. Start the console.
a. Remove all jobs and events registered against the machine the agent
is running on.
b. As soon as all events and jobs have been removed, the console can be
closed again.
2. Stop the Intelligent Agent on the machine.
A pre-9.0.1 Agent on Unix can be stopped by issuing the command:
$ lsnrctl dbsnmp_stop
A 9.0.1 or later Agent on Unix can be stopped by issuing the command:
$ agentctl stop
After the command has been issued, verify with the 'ps' command that
all 'dbsnmp' processes have indeed been stopped.
$ ps –ef |grep dbsnmp
NOTE: If the Intelligent Agent cannot be stopped, use the 'ps' command
to get the process ID's of the DBSNMP processes, and use the 'KILL -9'
command to terminate these processes.
On Windows NT/2000, use the Control Panel / Services applet, or issue
the command line option:
C:\> NET STOP "name of the agent service"
If you are not sure about the name of the Agent service, issue a 'NET
START' command, or check the Services applet for the services that are
running. When the agent is stopped, verify with the TaskManager that the
dbsnmp processes have indeed been stopped. If the Intelligent Agent can
not be stopped via the NET STOP command, the only way to terminate the
Agent then, is to use the 'KILL' command. The KILL utility is provided
in the Windows NT Resource Kit.
C:\> KILL -f DBSNMP
3. Go to the "$ORACLE_HOME/network/agent" directory. In this directory,
delete the following files:
services.ora
*.q
*.inp
*.jou
out*
tcl*
dbsnmp.ver
SERVICES.ORA
This file contains all the services the agent has discovered. This file
will be recreated the next time the agent starts.
*.q
These files are the binary representation of all registered and running
jobs and events. The agent creates new fresh files on startup when they
do not exist. Information about the host the agent is running on is
stored in these files. If the name or the IP address of the agent
machine changes, these files need to be recreated.
*.inp
These files are parameter files for registered jobs.
*.jou
These files are journal files with information the agent will use to
execute jobs.
out*
These files are temporary output files. These files are generated when
jobs are being executed and should be automatically removed by the agent
after a job finishes.
tcl*
These files are TCL template scripts, including the specific commands
specified in the job send to the agent. There are *.tcl files in other
directories – DO NOT delete the other TCL files. They are scripts that
ship with the Agent.
DBSNMP.VER
This file is a text file with the agent version information. This file
will also be recreated when the agent starts again.
NOTE: DO NOT DELETE the SVPPCART.DAT file that exists with 9.0.1 and
later Agents. This file is the definition file for the Agent’s Data
Gatherer Cartridge and is not generated by the Agent.
4. Next, go to the "$ORACLE_HOME/network/admin" or "TNS_ADMIN"
directory and remove the following files:
SNMP_RO.ORA
This file contains read-only information about the Agent’s discovered
services on the machine. This file should never be manually edited!
During startup, this file is read if it exists, and then recreated again
with the new discovery information.
SNMP_RW.ORA
This file contains read-write information about the Agent’s
discovered services on the machine. Some of the information in this file
can be edited by an administrator to provide additional information like
tracing / logging and hostname resolution, etc. During startup, this
file is also read if it exists and new discovery information is appended
to the file.
5. In order to have a good idea of the things the agent has logged and
reported during startup, it is advised to either rename or remove the
existing log files the agent has already created. The following files,
all located in the "$ORACLE_HOME/network/log" directory and are used
during startup of the agent:
Pre 9.0.1 Agents:
- NMICONF.LOG Discovery log files
- NMI.LOG: SQL*Net connection errors
- DBSNMPC.LOG: Communication thread logging, if logging is enabled
- DBSNMPW.LOG: Working thread logging, if logging is enabled
9.0.1 and later Agents:
AGENTSRVC.LOG A Windows NT/2000 file that shows startup errors
DBSNMP.LOG Communication and Work thread logging is in one file
NMICONF.LOG Discovery log files
Oracle<home>90Agent.nohup Agent startup errors.
6. Check the $ORACLE_HOME/network/library directory for any core dumps.
If they exist, remove them.
7. Recreate an empty SNMP_RO.ORA file. Add this single line in the
file:
snmp.visibleservices = ()
8. If tracing is needed to debug a certain situation, a new
"SNMP_RW.ORA" can be created, with the debug parameters:
Pre-9.0.1 Agents:
nmi.trace_level=16
nmi.trace_unique=true
9.0.1 or later Agents:
dbsnmp.trace_level=16
dbsnmp.trace_unique=true
9. Restart the Agent. After the agent has started, verify the
"SERVICES.ORA" file first. If this file contains all the services on the
machine, then check the "SNMP_RO.ORA" and "SNMP_RW.ORA" files. Discovery
problems can be found in the file "NMICONF.LOG".

It was helpful, now I have Oracle 9.2.0.3 on SuSe 9.1, all works fine. I already tested my application on it.

Так, установил оракл 9.2.0.4 на сусю 9.1 SLES. Похоже, но все же несколько иначе:

Начало такое же как и для 9.2.0.1, другой сам процесс инсталяции.

Installation of oracle:

1) Run runInstaller. Use all settings as you wish except database creation. Skip it.

2) During the linking you will meet 2 errors, related with ins_rdbms.mk and ins_net_client.mk. Ignore it.
3) When the prompt of running root.sh appeared – to do the following


However the bug with dnsnmp is not fixed yet. You should to apply 2 patches (#2617419 and #3238244) there.


and run

[src]>su - root
>cd $ORACLE_HOME
>./root.sh
[src]
4) The installation should be finished correctly, go to post-installation steps.


Вобщем все, уже рабочая инсталяция. Особых танцев с бубном не надо.