SAP - common problem


Alert log for TeltankUSA is on \\cyanide\d$\orant\rdbms73\trace\tt32ALRT.log

Common problem is that the database is hanging to can't come up if the log archive directory is full.

Directory to check is \\cyanide\e$\Oradata\tt32\Arch.

message you get in alert log is :

ora-255 signalled during : alter database "TT32" open ....
dump file d:\orant\rdbms73\trace\tt32alrt.log

Further up there may be other messages to say archive directory is full & archve is stopped.
Europe
Ask the ops to check that e: drive on Europe is not full.

If it is full very old archive logs must either be deleted or moved before the database can come up or continue to operate. To continue stop and restart Oracle Services on Europe.

We have no terminal Service access to Europe so you have to ask the ops to do the actions.

SAP System Availability Monitor
Adding a system to the SAP monitor
SAP System Availability Monitor
Adding a system to the SAP monitor

From a telnet session:

sign on to oramon

su – monadm (note you may have to su – first…)
execute the following script, this will prompt for information:
./addsys2mon

Create entries for SAP monitor
System ID (PXZ) : ASH
Geography (Global) : global
Description (CRM Dev.) : test system
Node ID (spn123c) : spn666c
Client Number (001) : 090
System Number (99) : 99

once system number has been added, the following will appear:
=== Using the following information ===

SAP SID : ASH
Geography : global
Description : test system
Node ID : spn666c
Client no. : 090
Sytem Number: 99

Do you wish to create an entry with these details (y/n) :
enter y or n as appropriate (n will discard entry)
If you entered y, an SQL script will run and add the entries into the database with a user ID of sapmon and a password of rhu8ar85
Creating additional nodes for a system
To create additional nodes for the system, the SQL script /cob/bin/addanode.sql can be used from an SQL session. You will need to start an SQL session as user sapmon (password ‘p’ word). The script doesn’t loop, so it needs to be run once per additional node you want to add.
SQL> @/cob/bin/addanode
Enter SAP SID : ASH
Enter node ID : spn999c
note: this script will leave you at an SQL> prompt, enter quit to close
Setup SAP user ID and password
Once this has been done, the user needs to be created in the SAP system and the password set. Remember to log on and off with this user to change the initial password (so make sure the initial password ISN’T rhu8ar85 !)
Add new data to Ops monitor (or refreshing data)
Now the data needs to be added to the monitor, so use the LoadData button on the monitor GUI to refresh the system/node list.
Disabling a system on the monitor
Occasionally, it may be useful to turn off monitoring on a particular system. To do this, start an SQL session as sapmon and run the following script:
SQL> @/cob/bin/setmon2no
Enter SAP SID to disable on monitor : ASH
this will update the check flag on the database, so again, the Ops monitor needs to be refreshed.
Enabling a system on the monitor
If a system has had monitoring “turned off” it can be re-enabled from an SQL session using the following script:
SQL> @/cob/bin/setmon2yes
Enter SAP SID to enable on monitor : ASH
this will update the check flag on the database, so again, the Ops monitor needs to be refreshed.

Please note that both of these will leave you at an SQL> prompt, so type quit to exit

Which t-code is used to maintain system profile ??

Which t-code is used to maintain system profile ??

I would like to set some profile parameters in system profile(not user profile). Is there anyone

know which t-code is for this.
+++++++++++++

Try RZ10, RZ11
++++++++++++

please use transaction RZ11.
++++++++++++++++++++++++++++

Hi,

In RZ10, there are more than one profile, which one is used. and it seems the profiles are all

created automatically.

In RZ11, I can only display, but not change. And how the change in RZ11 have an effect in system

profiles?

+++++++++++++++++++++++++++++++++++++++++++

There are default, startup and instance profiles.
You change parameters for profile by choosing 'extended maintanence'.

++++++++++++++++++++++++
Could you please tell me the different usage of default, startup and instance profiles.
which one I should change. And what about my second qustion in RZ11 in above message.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Profile administration is done via RZ10.
You can change via RZ11.

Startup profile:
In format START_. It used to specify the parameter for each

instances of the processes to be started. E.g MS and Disp.

Instance profile:
In format _.
It contains parameters that apply to one instance.

Default profile:
In format DEFAULT.PFL. It has global parameters that apply to all instances.

They are store in \usr\sap\\SYS\profile directory.

eg for windows : C:\usr\sap\D11\sys\profile


+++++++++++++++++++++++++++++++++++

But in RZ11, parameters can only be displayed.
Please check.

+++++++++++++++++++++++++++++++++++++

which parameter you would like to change ?
Do you have authorization to change that parameter ?
+++++++++++++++++++++++++++++++++

I have all the authorizaiton. and after run RZ11, I run SU53, got "All authorization checks have

so far been successful" message.

After run RZ11, the title is maintain profile parameters.
but at below, there is only display button.
I choose parameter rec/client, or any other else, I could not change the value but only display.

I cannot find the button or menu path to change.

++++++++++++++++++++++++++++++++++++++

Not all profile can be changed dynamically.
In RZ11, those that can be changed dynamically will have "Change value" button.
You can check in RZ11, after clicking the "Display", see whether the checkbox for
"DynamicallySwitchable" is checked.

For parameter rec/client, it is not changed dynamically.
(Note: if you go to SE38, run report RSPFPAR, and enter rec/client, then press execute (F8), you

will see the info there.)

In this case, then you need to go to RZ10 to add parameter rec/client into instance profile, to

overwrite the system default value. (By default, it should not display in parameter list in

instance profile, unless it is user defined.)

Of course, you need to restart the instance upon changes in instance profile.

+++++++++++++++++++++++++++++++++++++++++++++