OS Installation - Linux

8/7/2019 OS Installation - Linux

1/139

Vi /etc/sysconfig/network


2/139


3/139

Linux Kernel parameters

vi /etc/sysctl.conf


4/139

Process resource limits

vi /etc/security/limits.conf


5/139

Other parameters changes


6/139

Applying patch : rhl_pre_install.sh


7/139

Installing java j2sdk_1_4_2_12-linux-i586.rpm

export JAVA_HOME


8/139

starting sap installer


9/139


10/139


11/139


12/139


13/139


14/139


15/139


16/139


17/139


18/139


19/139


20/139


21/139


22/139


23/139

made directories trans .... /oracle/PRD/920_32


24/139


25/139


26/139


27/139


28/139

now using the latest version of sapinst from marketplace


29/139


30/139


31/139


32/139


33/139


34/139


35/139


36/139


37/139


38/139


39/139


40/139


41/139


42/139


43/139


44/139


45/139


46/139


47/139


48/139

installation of database instance


49/139


50/139


51/139


52/139


53/139


54/139


55/139


56/139


57/139


58/139


59/139


60/139


61/139


62/139


63/139


64/139


65/139


66/139


67/139


68/139


69/139


70/139


71/139


72/139


73/139


74/139


75/139


76/139


77/139


78/139


79/139


80/139


81/139


82/139


83/139


84/139


85/139


86/139


87/139


88/139


89/139


90/139


91/139

like above 12-13 error windows came just ignore it and run the rootsh script


92/139

now after installation click


93/139

patch was not installed so following error came

now installing the patch


94/139


95/139


96/139


97/139


98/139


99/139


100/139


101/139


102/139


103/139

there was one error shared memory which is given above. The error was resolved when we changed the

size of sga, shared pool, etc in initPRD.ora in oracle_home/dbs/ directory. The reason is when we give

size of memory more than 4GB then we have to reduce the size manually.

In our case the size is 8 GB so we reduced that. This occurred on 19th phase, now installation is running

fine.


104/139

This error came because brconnect tool was not working in /sapmnt/PRD/exe or

/usr/sap/PRD/SYS/exe/run (kernel) dowloaded fresh tool from marketplace but it was not working

because SAPCAR was of old version..downloaded new SAPCAR from marketplace and then it workedsee the screenshot.. I referred these two notes...

212876 for SAPCAR and this sdn link

https://www.sdn.sap.com/irj/sdn/thread?threadID=299487. After that it executed and is running fine..
https://www.sdn.sap.com/irj/sdn/thread?threadID=299487https://www.sdn.sap.com/irj/sdn/thread?threadID=299487


105/139


106/139

this error was solved by simply stopping and restarting the sapinst


107/139


108/139


109/139


110/139

The installation went well now try to loginto the system


111/139


112/139


113/139


114/139

starting BR*tools


115/139

5


116/139

4


117/139

c


118/139

c


119/139

1


120/139

I'll try to take the backup first of the existing fresh database before doing anything .. I have stopped the

SAP intance


121/139

4

1


122/139

change the options accordingly

c


123/139


124/139


125/139

changed the permissions now running the backup again


126/139

Again I changed permissions as a root user. Earlier I was changing the permissions as oraprd user.


127/139


128/139


129/139


130/139


131/139

I talked to vinayak and he said because of the profiles it is not taking the backup. Now I am going tocopy the profile from production server and try again.

The restore worked out like this :

instead of copying all the three files

bdxiukbt (dir) 7.8G

PRD (dir) 96K

bdxiukbt.aft (file) 28K

Don't copy bdxiukbt.aft (file) because it is corrupted and the Brtools try to read from this file and loststhe way the option we choose is 4. whole database reset.

From the PRD directory we copied two files

bdxiukbt.afd and backPRD.log

and started the process.. it completed successfully.

Glimpses after installation


132/139


133/139


134/139


135/139

After restoring the database for 100 client to be the logon client we added the parameter

login/system_client in Default profile of the ecctest server. We also selected the option activate active

profiles and it worked. Now all the configurations and users are restored from production server to thetest server and the test server has become clone of the production server. Now we are ready for the

Database upgrade.

Database Upgrade to Oracle 10g Release (10.2) : UNIX


136/139


137/139


138/139


139/139

OS Installation - Linux

Documents

Transcript of OS Installation - Linux