Sajt u izradi …
Smart assist
Rad sa smart assist-om
————————-
Prvo hocu da u HA Aplikacije stavim Oracle. Da bi Smart assist detektovao Oracle bazu, potrebno je ekxportovati sledece varijable:
export DB_SID=EX1
export ORACLE_SID=EX1
export ORACLE_BASE=/oracle
export ORACLE_HOME=/oracle/EX1/112_64
export NLS_LANG=AMERICAN_AMERICA.UTF8
export dbms_type=ORA
export dbs_ora_tnsname=EX1
export dbs_ora_schema=SAPSR3
export ORACLE_USER=oraex1
Pored env varijabli pre pokretanja smart assist-a za oracle potrebno je da:
– Oracle polje bude mountovano (mount kroz klaster – dici online resurse sa pripadajucom volume grupom, ne moze da se podigne kroz os.)
Oracle Database Smart Assist # aix71node1 aix71node2
Izabrati Automatic discovery
i onda ID za Oracle bazu (u nasem slucaju EX1)
Nakon ubacivanja Oracle aplikacije u HA, staru resurs grupu koju smo iskoristili samo za mountovanje Oracleta mozemo da obrisemo. A mozemo i da ostavimo da nam bude zgodno za rucno podizanje….
——-
Prilikom pokretanja smart assist za SAP vazno je da:
– nfs bude mountovan po pravilima (GFS) (lokalna polja /export/sapmnt/SID i /export/saptrans su exportovana prema /sapmnt/SID i /usr/sap/trans)
– env varijabla bude eksportovana : export SAPSYSTEMNAME=EX1
Desio mi se problem sa nedetektovanjem ASCS servisa iako rucno startovan radi bez problema, utrosio sam dosta vremena na ovo… ali nasao resenje
Iz skripte koja detektuje service nasao sam deo koji radi detekciju (ne pise ovako, to sam izvukao iz skripte, i to kad uradim export VERBOSE_LOGGING=”High”)
skripta za detekciju se nalazi u /usr/es/sbin/cluster/sa/sap/sbin i pokrece se sa:
./cl_sapdiscover -t SERVIS, npr
./cl_sapdiscover -t SCS ili ./cl_sapdiscover -t ERS ili ./cl_sapdiscover -t AS …. ili GFS za global file systems
Razrada problema:
aix71node1:/usr/sap/EX1/SYS/profile#ps -aef | grep ‘/usr/sap/EX1/ERS10/profile/EX1_ERS10_aix71node2’ | grep sapstartsrv
ex1adm 4128922 1 0 11:38:50 – 0:05 /usr/sap/EX1/ERS10/exe/sapstartsrv pf=/usr/sap/EX1/ERS10/profile/EX1_ERS10_aix71node2 -D -u ex1adm
i ovo je ok, ERS servise je detektovao …..
ALI ZA ASCS00 nije:
aix71node1:/usr/sap/EX1/SYS/profile#ps -aef | grep ‘/usr/sap/EX1/SYS/profile/’ | grep sapstartsrv
prazno ???
Onda pogledah u /usr/sap/sapservices i vidim da je upisam profil EX1_ASCS00_ex1app, a u stvari skripta trazi ono sto je navedeno u /usr/sap/services
A ono sto se vrti svo vreme je:
aix71node1:/usr/sap/EX1/SYS/profile#ps -aef | grep ‘/usr/sap/EX1/SYS/profile/START_ASCS00_ex1app’ | grep sapstartsrv
ex1adm 13893664 1 0 11:52:13 – 0:06 /usr/sap/EX1/ASCS00/exe/sapstartsrv pf=/usr/sap/EX1/SYS/profile/START_ASCS00_ex1app -D
Zamenio sam u /usr/sap/services EX1_ASCS00_ex1app sa START_ASCS00_ex1app, sve oborio i restartovao, nakon toga prolazi detekcija i imamo sledecu sliku u smitty-u ….
Make Applications Highly Available (Use Smart Assists)
Move cursor to desired item and press Enter.
Add an Application to the PowerHA SystemMirror Configuration
Change/Show an Application’s PowerHA SystemMirror Configuration
Remove an Application from the PowerHA SystemMirror Configuration
Manage Your Applications
Change/Show the Resources Associated with Your Application
SAP liveCache Hot Standby Configuration Wizard
Test Your Application for Availability
+————————————————————————–+
| Select The Specific Configuration You Wish to Create |
| |
| Move cursor to desired item and press Enter. |
| |
| 4.SAP NW 7.0 AS Instance # aix71node1 aix71node2 |
| 3.SAP NW 7.0 ERS Instance # aix71node1 |
| 1.SAP NW 7.0 Global Filesystem # aix71node1 aix71node2 |
| 2.SAP NW 7.0 SCS Instance # aix71node1 |
| |
Detektovao je sve sto treba :-)… znaci dobro obratiti paznju na /usr/sap/services, env varijable i servise koji rade u background-u.