Upgrading and Migrating an IQ database from older ... - Sybase
Upgrading and Migrating an IQ database from older ... - Sybase
Upgrading and Migrating an IQ database from older ... - Sybase
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
ASE 15 Upgrade Checklist for <strong>Upgrading</strong> <strong>from</strong> ASE 12.x <strong>Sybase</strong> ASE 15<br />
_________________________________________________________________________________________________<br />
For more details on the use of SySAM, please see the following product Guides:<br />
o<br />
o<br />
o<br />
For information on Generating Licenses at SPDC (in the SySAM Users Guide), see:<br />
http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc00530.0200/doc/html/jon<br />
1271803489638.html<br />
For SySAM pre-installation pl<strong>an</strong>ning <strong><strong>an</strong>d</strong> SySAM installation information, see the SySAM Users<br />
Guide at:<br />
http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc00530.0200/doc/html/titl<br />
e.html<br />
For Troubleshooting, see the Troubleshooting chapter in the ASE 15.7 Installation Guide for<br />
your platform. For example, see Adaptive Server Enterprise 15.7 > Installation Guide Adaptive<br />
Server Enterprise 15.7 for Linux > at<br />
http://infocenter.sybase.com/help/topic/com.sybase.infocenter.help.ase.15.7/title.htm<br />
2.2.8: DETECT SYSAM ERRORS AND TAKE THE APPROPRIATE ACTION<br />
To avoid interruptions in service, it is CRITICAL that you regularly sc<strong>an</strong> your log for SySAM messages <strong><strong>an</strong>d</strong><br />
take the appropriate action to resolve <strong>an</strong>y error messages or warnings. Therefore, consider the<br />
following:<br />
SySAM performs licensing checks at various times during the server’s runtime cycle:<br />
o<br />
o<br />
Some licenses are checked at startup, some upon access of the feature <strong><strong>an</strong>d</strong> some are<br />
checked at both times.<br />
Licenses are also checked periodically during the server’s runtime according to a<br />
“heartbeat” interval of 2 to 24 hours. When invoked, a mech<strong>an</strong>ism checks for <strong>an</strong>y ch<strong>an</strong>ges<br />
<strong><strong>an</strong>d</strong> updates to ASE licenses.<br />
Because SySAM checks for license issues on a regular basis during the server’s run cycle, SySAM errors<br />
c<strong>an</strong> be detected <strong><strong>an</strong>d</strong> reported at <strong>an</strong>y time:<br />
o<br />
o<br />
o<br />
When a message is issued, it is import<strong>an</strong>t that you take the appropriate action in a timely<br />
m<strong>an</strong>ner.<br />
All SySAM-related errors are printed in the ASE error log <strong><strong>an</strong>d</strong> are prefixed with "kernel<br />
SySAM:”. For example:<br />
kernel SySAM: Failed to obtain 1 license(s)<br />
For ASE_CORE feature <strong>from</strong> license file(s) or server(s).<br />
If e-mail alerts are configured, recipients also receive <strong>an</strong> e-mail whenever a SySAM event<br />
occurs.<br />
o<br />
o<br />
o<br />
When a license problem is first noted, ASE provides a 30-day grace period <strong>from</strong> the time of<br />
build, if applicable.<br />
SySAM error messages will provide date information to indicate if <strong><strong>an</strong>d</strong> when ASE will be<br />
shutdown. Perm<strong>an</strong>ent licensing will support a runnable grace or run-time grace period.<br />
To avoid interruptions in service, it is CRITICAL that you regularly sc<strong>an</strong> your log for SySAM<br />
messages <strong><strong>an</strong>d</strong> take the appropriate action to resolve <strong>an</strong>y error messages or issues.<br />
___________________________________________________________________________________________________________<br />
ASE 15 Upgrade Checklist for ASE 12.X v3.0 Page 57 of 97 Last Update: May, 2012