<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;DEQMSHs5fSp7ImA9WhRaFEw.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551</id><updated>2012-02-16T23:49:49.525+05:30</updated><category term="Spool Management" /><category term="SAP Connect" /><category term="SAP Material / Software" /><category term="SAP Notes" /><category term="Solution Manager" /><category term="High Availability" /><category term="SAP XI/PI" /><category term="RFC" /><category term="SAP Basics" /><category term="FAQs" /><category term="Livecache" /><category term="Portal" /><category term="Database" /><category term="Background Jobs" /><category term="CCMS and Monitoring" /><category term="How to...." /><category term="Java / Web AS" /><category term="Transport Management" /><category term="Miscellaneous" /><category term="Memory Management" /><category term="Security" /><category term="ABAP and Data Dictionary" /><category term="Netweaver" /><title>SAP BASIS &amp; Security</title><subtitle type="html" /><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://sapbasis-security.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>375</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/blogspot/qxrf" /><feedburner:info uri="blogspot/qxrf" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>blogspot/qxrf</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><entry gd:etag="W/&quot;DEEFSHk_fyp7ImA9WhRaFE0.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-1624341011827887338</id><published>2012-02-16T21:06:00.001+05:30</published><updated>2012-02-16T21:06:59.747+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-16T21:06:59.747+05:30</app:edited><title>BR*Tools for Oracle DBA</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/1624341011827887338/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/02/brtools-for-oracle-dba.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/1624341011827887338?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/1624341011827887338?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/ULAz99NOiuk/brtools-for-oracle-dba.html" title="BR*Tools for Oracle DBA" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html"> The BR*Tools are installed automatically on the database server in the directory /usr/sap/&amp;lt;SAPSID&amp;gt;/SYS/exe/run. We classify BR*Tools as functional, help, batch, and interactive tools: Tool Types for BR*Tools  Type Tool Description Functional BRBACKUP, BRARCHIVE, BRRESTORE, BRRECOVER, BRSPACE, and BRCONNECT Perform actions directly on database files or objects Help BRTOOLS and BRCONNECT ●      
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/8z6dx-T2KIGo6ekC4JsajjMGhwM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/8z6dx-T2KIGo6ekC4JsajjMGhwM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/8z6dx-T2KIGo6ekC4JsajjMGhwM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/8z6dx-T2KIGo6ekC4JsajjMGhwM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/02/brtools-for-oracle-dba.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEMGR30_eip7ImA9WhRaFE0.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-793013827894302863</id><published>2012-02-16T21:03:00.001+05:30</published><updated>2012-02-16T21:03:46.342+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-16T21:03:46.342+05:30</app:edited><title>SAP Naming Conventions for Tablespaces and Data Files</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/793013827894302863/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/02/sap-naming-conventions-for-tablespaces.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/793013827894302863?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/793013827894302863?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/sYJy_Pqkyzo/sap-naming-conventions-for-tablespaces.html" title="SAP Naming Conventions for Tablespaces and Data Files" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html"> Tablespace Naming Convention as of SAP Web Application Server 6.10 The following table contains an overview of all the tablespaces in an SAP system and how they are used:  Tablespace Name Use SYSTEM  Oracle system tablespace SYSAUX  Oracle auxiliary system tablespace PSAPTEMP  Temporary obejcts (system default temporary tablespace) PSAPTEMP&amp;lt;name&amp;gt;  Additional temporary objects, if required. 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/eu2fIwdoGX0dxqX4l13xwXLWT0Y/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/eu2fIwdoGX0dxqX4l13xwXLWT0Y/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/eu2fIwdoGX0dxqX4l13xwXLWT0Y/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/eu2fIwdoGX0dxqX4l13xwXLWT0Y/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/02/sap-naming-conventions-for-tablespaces.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEUNRn8-fCp7ImA9WhRaFE0.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-8102099808862733725</id><published>2012-02-16T21:01:00.001+05:30</published><updated>2012-02-16T21:01:37.154+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-16T21:01:37.154+05:30</app:edited><title>Operating System Users and Groups &amp; Database Users and Roles</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/8102099808862733725/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/02/operating-system-users-and-groups.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/8102099808862733725?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/8102099808862733725?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/KnC5QEUhmhI/operating-system-users-and-groups.html" title="Operating System Users and Groups &amp; Database Users and Roles" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html">Operating System Users In the SAP system the roles of the users ora&amp;lt;dbsid&amp;gt; and &amp;lt;sapsid&amp;gt;adm on UNIX, or &amp;lt;sapsid&amp;gt;adm and SAPSERVICE&amp;lt;SID&amp;gt; on Windows, used to be separate. Due to the requirements for RMAN backup, this is no longer true. Both users now belong to the operating system groups dba andoper, as shown in the tables below.  Database Roles ·        SYSDBA All authorizations·        SYSOPER 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/4X0xYLTfsfJT6krxEMyxZlstP9g/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/4X0xYLTfsfJT6krxEMyxZlstP9g/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/4X0xYLTfsfJT6krxEMyxZlstP9g/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/4X0xYLTfsfJT6krxEMyxZlstP9g/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/02/operating-system-users-and-groups.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEYFQH85fip7ImA9WhRaFE0.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-2994890134464606099</id><published>2012-02-16T20:58:00.001+05:30</published><updated>2012-02-16T20:58:31.126+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-16T20:58:31.126+05:30</app:edited><title>Oracle Database Directory Structure (UNIX)</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/2994890134464606099/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/02/oracle-database-directory-structure_16.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/2994890134464606099?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/2994890134464606099?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/FW_1KI1elpE/oracle-database-directory-structure_16.html" title="Oracle Database Directory Structure (UNIX)" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html">This section describes the directory structure for the Oracle database with the Windows operating system.  The directories contain a range of files such as profiles, log files, scripts, executables, and so on. The following conventions apply to this section:  Term Meaning %&amp;lt;name&amp;gt;%  Environment variable &amp;lt;DBSID&amp;gt;  %$ORACLE_DBSID%  &amp;lt;TSP&amp;gt;  Tablespace short name For example, BTABD for the tablespace 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/fAO_DKgDLc81JCuL2729MoRpd-I/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/fAO_DKgDLc81JCuL2729MoRpd-I/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/fAO_DKgDLc81JCuL2729MoRpd-I/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/fAO_DKgDLc81JCuL2729MoRpd-I/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/02/oracle-database-directory-structure_16.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEcFSX44eCp7ImA9WhRaFE0.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-3462600529191161461</id><published>2012-02-16T20:56:00.001+05:30</published><updated>2012-02-16T20:56:58.030+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-16T20:56:58.030+05:30</app:edited><title>Oracle Database Directory Structure (UNIX)</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/3462600529191161461/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/02/oracle-database-directory-structure.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/3462600529191161461?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/3462600529191161461?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/PmNZxSG65qk/oracle-database-directory-structure.html" title="Oracle Database Directory Structure (UNIX)" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html">This section describes the directory structure for the Oracle database with the UNIX operating system.  The directories contain a range of files such as profiles, log files, scripts, executables, and so on. The following conventions apply to this section:  Term Meaning $&amp;lt;name&amp;gt;  Environment variable &amp;lt;DBSID&amp;gt;  $ORACLE_SID  &amp;lt;TSP&amp;gt;  Tablespace short name For example, BTABD for the tablespace PSAPBTABD.
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Mcgdme-KlYthpc2n9JKoK0ODq5o/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Mcgdme-KlYthpc2n9JKoK0ODq5o/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Mcgdme-KlYthpc2n9JKoK0ODq5o/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Mcgdme-KlYthpc2n9JKoK0ODq5o/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/02/oracle-database-directory-structure.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D08HQ3Y-fyp7ImA9WhRaFE0.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-9025482971930200021</id><published>2012-02-16T20:53:00.001+05:30</published><updated>2012-02-16T20:53:52.857+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-16T20:53:52.857+05:30</app:edited><title>Environment Variables (Windows) for Oracle database and BR*Tools</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/9025482971930200021/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/02/environment-variables-windows-for.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/9025482971930200021?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/9025482971930200021?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/1hZdNsgpnP0/environment-variables-windows-for.html" title="Environment Variables (Windows) for Oracle database and BR*Tools" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html">Environment variables define parameter values used by the Oracle database and BR*Tools. This section describes the variables used when the operating system is Windows.  The database uses the parameter values for many different purposes. BR*Tools also uses the parameter values. The following variables are required: ·        ORACLE_SID System ID of the database instance Example: C11 SAPSID or 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/lIaGD6H5IumfZEY7oANhfZNray0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/lIaGD6H5IumfZEY7oANhfZNray0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/lIaGD6H5IumfZEY7oANhfZNray0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/lIaGD6H5IumfZEY7oANhfZNray0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/02/environment-variables-windows-for.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0ACQ38zfyp7ImA9WhRaFE0.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-4878393464472896282</id><published>2012-02-16T20:52:00.001+05:30</published><updated>2012-02-16T20:52:42.187+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-16T20:52:42.187+05:30</app:edited><title>Environment Variables (UNIX) for Oracle database and BR*Tools</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/4878393464472896282/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/02/environment-variables-unix-for-oracle.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/4878393464472896282?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/4878393464472896282?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/CJxTNPybcE4/environment-variables-unix-for-oracle.html" title="Environment Variables (UNIX) for Oracle database and BR*Tools" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html">Environment variables define values used by the Oracle database and BR*Tools. This section describes the variables used when the operating system is UNIX.  The database uses the environment values for many different purposes. BR*Tools also use the values. The following variables are required: ·        ORACLE_SID System ID of the database instance Example: C11 SAPSID or sapsid refers to the SAP 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/UItXeuoJ2gwJdHORiFBOqZBh_f4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/UItXeuoJ2gwJdHORiFBOqZBh_f4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/UItXeuoJ2gwJdHORiFBOqZBh_f4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/UItXeuoJ2gwJdHORiFBOqZBh_f4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/02/environment-variables-unix-for-oracle.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0IMR34zeyp7ImA9WhRaFE0.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-8908840373614014524</id><published>2012-02-16T20:49:00.001+05:30</published><updated>2012-02-16T20:49:46.083+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-16T20:49:46.083+05:30</app:edited><title>Starting BR*Tools</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/8908840373614014524/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/02/starting-brtools.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/8908840373614014524?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/8908840373614014524?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/szKMD7pBltU/starting-brtools.html" title="Starting BR*Tools" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html">You can use this procedure to start BR*Tools for Oracle. You can only use BR*Tools to manage a database system that is running on the same host system.  Check the below points before starting BR*Tools ·        Make Sure you have configured: ¡        The database system ¡        BR*Tools  ·        Logon user You can log on as the operating system user who owns the data files of the database system
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/-PaFRAI4hC8OCfwvq_Pb74zYXTM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/-PaFRAI4hC8OCfwvq_Pb74zYXTM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/-PaFRAI4hC8OCfwvq_Pb74zYXTM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/-PaFRAI4hC8OCfwvq_Pb74zYXTM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/02/starting-brtools.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk4BRnk6fCp7ImA9WhRaFE0.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-949555165508101870</id><published>2012-02-16T20:39:00.001+05:30</published><updated>2012-02-16T20:39:17.714+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-16T20:39:17.714+05:30</app:edited><title>Configuration of BR*Tools</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/949555165508101870/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/02/configuration-of-brtools.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/949555165508101870?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/949555165508101870?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/HHk00pJILeA/configuration-of-brtools.html" title="Configuration of BR*Tools" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html">To get started with BR*Tools, you need to configure it.  Prerequisites ·        You have made any required settings in the initialization profile. The default Initialization Profile init&amp;lt;DBSID&amp;gt;.dba is: UNIX: &amp;lt;ORACLE_HOME&amp;gt;/dbs/init&amp;lt;DBSID&amp;gt;.sap Windows: %&amp;lt;ORACLE_HOME&amp;gt;%\database\init&amp;lt;DBSID&amp;gt;.sap Changes to profile parameters become active when you start BR*Tools.  ·        You have set the environment
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/E_76t1IKa2dXoUwB4Z5ZCPe_ahU/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/E_76t1IKa2dXoUwB4Z5ZCPe_ahU/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/E_76t1IKa2dXoUwB4Z5ZCPe_ahU/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/E_76t1IKa2dXoUwB4Z5ZCPe_ahU/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/02/configuration-of-brtools.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkEDQHw8eip7ImA9WhRaFE0.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-5524998143182719914</id><published>2012-02-16T20:34:00.001+05:30</published><updated>2012-02-16T20:34:31.272+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-16T20:34:31.272+05:30</app:edited><title>Oracle Restore and Recovery for SAP</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/5524998143182719914/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/02/oracle-restore-and-recovery-for-sap.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/5524998143182719914?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/5524998143182719914?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/7RUP1hAEMzE/oracle-restore-and-recovery-for-sap.html" title="Oracle Restore and Recovery for SAP" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html">This section helps you to develop an approach to restore and recover of your Oracle database in the event of failure.  Always analyze the problem carefully before attempting to recover your database. If in doubt, seek support from SAP. The business costs of an incorrect or delayed recovery can easily outweigh consultancy fees.  We strongly recommend you to practice restore and recovery on a test 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/IH8dKVHwghoVNgNgopTeCEiKSCY/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/IH8dKVHwghoVNgNgopTeCEiKSCY/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/IH8dKVHwghoVNgNgopTeCEiKSCY/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/IH8dKVHwghoVNgNgopTeCEiKSCY/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/02/oracle-restore-and-recovery-for-sap.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0cBRng5cSp7ImA9WhRaFEw.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-1747475889203171481</id><published>2012-02-01T00:21:00.002+05:30</published><updated>2012-02-16T23:27:37.629+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-16T23:27:37.629+05:30</app:edited><title>SAP eBooks Complete Collection (File4sharing Links)</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/1747475889203171481/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/02/sap-ebooks-complete-collection.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/1747475889203171481?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/1747475889203171481?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/_su2tMEIo78/sap-ebooks-complete-collection.html" title="SAP eBooks Complete Collection (File4sharing Links)" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html">



http://file4sharing.com/1gqvmv63vx0t/ABAP151 - ABAP Objects for
Java Developers.pdf.html
http://file4sharing.com/togone52q2wx/ABAP152 - Efficient Database
Programming with ABAP.pdf.html
http://file4sharing.com/hpdnhxb2lfpb/AC010 - Business Processes
in Financial Accounting.pdf.html
http://file4sharing.com/k41hqp8sfhdc/AC020 - Investment Management.pdf.html
http://file4sharing.com/nhve1veaqizp
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/54Zxa3PwlSLTSRGAj81nC4AvZb0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/54Zxa3PwlSLTSRGAj81nC4AvZb0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/54Zxa3PwlSLTSRGAj81nC4AvZb0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/54Zxa3PwlSLTSRGAj81nC4AvZb0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/02/sap-ebooks-complete-collection.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkIDRHY5eyp7ImA9WhRVEks.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-7923900092139444307</id><published>2012-01-11T13:26:00.001+05:30</published><updated>2012-01-11T13:26:15.823+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-11T13:26:15.823+05:30</app:edited><title>Client is not Available in this System</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/7923900092139444307/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/01/client-is-not-available-in-this-system.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/7923900092139444307?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/7923900092139444307?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/_uDJ_LcYOlY/client-is-not-available-in-this-system.html" title="Client is not Available in this System" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html"> Symptom You get an error " Client is not available in this system" when trying to login to the SAP system.  Solution Login to the SAP system using client 000. Execute transaction code SCC4 to check all the client list that are available in the system.    
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/BcpImbdNZaw8R8bW5aKjvOZuZhc/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/BcpImbdNZaw8R8bW5aKjvOZuZhc/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/BcpImbdNZaw8R8bW5aKjvOZuZhc/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/BcpImbdNZaw8R8bW5aKjvOZuZhc/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/01/client-is-not-available-in-this-system.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkMMQX05eCp7ImA9WhRVEks.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-670510871114208532</id><published>2012-01-11T13:24:00.001+05:30</published><updated>2012-01-11T13:24:40.320+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-11T13:24:40.320+05:30</app:edited><title>How to Check ABAP System Logs &amp; Traces</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/670510871114208532/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/01/how-to-check-abap-system-logs-traces.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/670510871114208532?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/670510871114208532?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/dJCHoMHcROY/how-to-check-abap-system-logs-traces.html" title="How to Check ABAP System Logs &amp; Traces" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html"> 1. During the starting of SAP system, events are written to log files. These files are extremely important from the point of view of identifying and troubleshooting problems. Logs of the SAP start process are stored in the file system and can be opened and read by the &amp;lt;SID&amp;gt;adm user.   2. Log file in Windows.   • Filepath where logs reside : &amp;lt;Drive&amp;gt;:\usr\sap\&amp;lt;Sys-ID&amp;gt;\DVEBMGS&amp;lt;Sys-Nr&amp;gt;\Work. • 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/S90DFEmYJlDsFyndRNDejYT4COU/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/S90DFEmYJlDsFyndRNDejYT4COU/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/S90DFEmYJlDsFyndRNDejYT4COU/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/S90DFEmYJlDsFyndRNDejYT4COU/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/01/how-to-check-abap-system-logs-traces.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkQHRHwyfyp7ImA9WhRVEks.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-2500624640473531843</id><published>2012-01-11T13:22:00.001+05:30</published><updated>2012-01-11T13:22:15.297+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-11T13:22:15.297+05:30</app:edited><title>How to Specify Update Server Name if Load Balancing is Deactivated</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/2500624640473531843/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/01/how-to-specify-update-server-name-if.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/2500624640473531843?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/2500624640473531843?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/gRP-zoxPZhs/how-to-specify-update-server-name-if.html" title="How to Specify Update Server Name if Load Balancing is Deactivated" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html">In the standard system, this parameter, rdisp/vbname specifies the name of an update server (set when the update server is created).  If rdisp/vb_dispatching is set to 0, the updates are only processed by the server in rdisp/vbname.  If the parameter has not been set correctly (not to an update server), this is reported when the installation check is performed (transaction sick ). You need to 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/REGhvLOZIBcPeTfHJh8-_A3rSWg/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/REGhvLOZIBcPeTfHJh8-_A3rSWg/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/REGhvLOZIBcPeTfHJh8-_A3rSWg/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/REGhvLOZIBcPeTfHJh8-_A3rSWg/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/01/how-to-specify-update-server-name-if.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkYCRX8-fSp7ImA9WhRVEks.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-3009458217271165076</id><published>2012-01-11T13:19:00.001+05:30</published><updated>2012-01-11T13:19:24.155+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-11T13:19:24.155+05:30</app:edited><title>SAP Start Job Conditions</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/3009458217271165076/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/01/sap-start-job-conditions.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/3009458217271165076?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/3009458217271165076?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/ULr4vNqUhQ0/sap-start-job-conditions.html" title="SAP Start Job Conditions" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-HCj6_RgKccU/Tw0_BOb8M0I/AAAAAAAAAiU/FwwdBEGLR84/s72-c/SAP%2BStart%2BJob%2BConditions-764156.jpg" height="72" width="72" /><thr:total>0</thr:total><content type="html"> Immediate This job will start as soon as possible, subject to job priority and the availability of background work processes. Users granted the appropriate authorizations for background processing can have their jobs released automatically as soon as they are scheduled, without special attention from a system administrator.   Date/time The job will start at the date and time specified, subject 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/jQzrzAZVlwCXmhh_GvFJ3voz8IE/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/jQzrzAZVlwCXmhh_GvFJ3voz8IE/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/jQzrzAZVlwCXmhh_GvFJ3voz8IE/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/jQzrzAZVlwCXmhh_GvFJ3voz8IE/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/01/sap-start-job-conditions.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU4FSX4_fip7ImA9WhRVEks.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-2897455011295371577</id><published>2012-01-11T13:15:00.001+05:30</published><updated>2012-01-11T13:15:18.046+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-11T13:15:18.046+05:30</app:edited><title>How to Configure &amp; Activate SAP TMS Backup Domain Controller</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/2897455011295371577/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/01/how-to-configure-activate-sap-tms.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/2897455011295371577?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/2897455011295371577?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/rcfxf3iMMm8/how-to-configure-activate-sap-tms.html" title="How to Configure &amp; Activate SAP TMS Backup Domain Controller" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html"> Configuring the Backup Domain Controller  Prerequisites In your transport domain, the SAP System that is configured as the domain controller is of special significance. If this SAP System fails, you cannot make changes to the TMS configuration during this time. Therefore if your transport domain contains more than three SAP Systems, we recommend configuring a backup domain controller. If your 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ud_IP8KqdIjETZQf6wGNsDbdzGM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ud_IP8KqdIjETZQf6wGNsDbdzGM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ud_IP8KqdIjETZQf6wGNsDbdzGM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ud_IP8KqdIjETZQf6wGNsDbdzGM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/01/how-to-configure-activate-sap-tms.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU8GSX84fSp7ImA9WhRVEks.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-398604101408126601</id><published>2012-01-11T13:13:00.001+05:30</published><updated>2012-01-11T13:13:48.135+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-11T13:13:48.135+05:30</app:edited><title>Recommended Buffer Quality in SAP System</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/398604101408126601/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/01/recommended-buffer-quality-in-sap.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/398604101408126601?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/398604101408126601?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/4tquDQpu76E/recommended-buffer-quality-in-sap.html" title="Recommended Buffer Quality in SAP System" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html"> The following describes how the buffer quality of the SAP buffers should be in a SAP System with good performance.   Repository buffers (nametab buffers) The qualities of the Repository buffers can reach 99.9% in a system that has been running for a few days. If the buffer quality is less than 95%, you should investigate the situation further. Check the: • Available freespace• Available 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/yOxomR5Y5DRi9_BEtTF1lKqFeHU/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/yOxomR5Y5DRi9_BEtTF1lKqFeHU/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/yOxomR5Y5DRi9_BEtTF1lKqFeHU/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/yOxomR5Y5DRi9_BEtTF1lKqFeHU/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/01/recommended-buffer-quality-in-sap.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUABQ3s8fCp7ImA9WhRVEks.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-7121032268473220034</id><published>2012-01-11T13:12:00.001+05:30</published><updated>2012-01-11T13:12:32.574+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-11T13:12:32.574+05:30</app:edited><title>STMS: Request is After End Mark</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/7121032268473220034/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/01/stms-request-is-after-end-mark.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/7121032268473220034?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/7121032268473220034?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/qJeLlLF1FBk/stms-request-is-after-end-mark.html" title="STMS: Request is After End Mark" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html"> Symptom Requests after the end mark are not imported during the next import. The end mark is automatically deleted only when the next import has completely ended. Afterwards, the requests can be imported.   Solution 1. Choose the transport request. Go to Queue &amp;gt; Move end mark. or 2. Open the import queue (the import queue may accidentally lock by user). Click on the lock icon (next to lorry icon
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/OwuqEN0UYq03uSHfmAN66Qz1t5Y/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/OwuqEN0UYq03uSHfmAN66Qz1t5Y/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/OwuqEN0UYq03uSHfmAN66Qz1t5Y/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/OwuqEN0UYq03uSHfmAN66Qz1t5Y/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/01/stms-request-is-after-end-mark.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUEDSXw6cCp7ImA9WhRVEks.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-5088302992439872845</id><published>2012-01-11T13:11:00.001+05:30</published><updated>2012-01-11T13:11:18.218+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-11T13:11:18.218+05:30</app:edited><title>How to test RFC authorization for TMSADM &amp; Reset TMSADM</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/5088302992439872845/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/01/how-to-test-rfc-authorization-for.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/5088302992439872845?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/5088302992439872845?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/uVk4wkIkYM8/how-to-test-rfc-authorization-for.html" title="How to test RFC authorization for TMSADM &amp; Reset TMSADM" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html"> Symptom When you try to execute authorization test for TMSADM in transaction code SM59, you see this error, " User TMSADM has no RFC authorization for function group SYST ". (SM59 -&amp;gt;  TMSADM@&amp;lt;SID&amp;gt;.DOMAIN_&amp;lt;DomainController &amp;lt;SID&amp;gt; -&amp;gt; Test Connection / Remote Logon)  Solution 1. Check the TMSADM authorization profile S_A.TMSADM is already assigned or not. The TMSADM must be check via client 000. 2. 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/vAZMpKYC2ArQItU2rQ6audViuWU/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/vAZMpKYC2ArQItU2rQ6audViuWU/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/vAZMpKYC2ArQItU2rQ6audViuWU/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/vAZMpKYC2ArQItU2rQ6audViuWU/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/01/how-to-test-rfc-authorization-for.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0cMQXgzeSp7ImA9WhRbEE8.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-3414631333768524812</id><published>2012-01-11T12:40:00.002+05:30</published><updated>2012-01-31T21:21:20.681+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-31T21:21:20.681+05:30</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="SAP Material / Software" /><title>Download SAP Training Simulators (Includes All Modules)</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/3414631333768524812/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2012/01/download-sap-training-simulators.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/3414631333768524812?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/3414631333768524812?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/ckCHd3QP5iQ/download-sap-training-simulators.html" title="Download SAP Training Simulators (Includes All Modules)" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/-052r_NlorK4/TlHowBTA0rI/AAAAAAAAAfE/_7olK6_h0X8/s72-c/SAP+Training+Simulator-729692.png" height="72" width="72" /><thr:total>0</thr:total><content type="html">









SAP Visual | 2008 | SAP iTutor Video files | 800x573 | English | 1376 files | SIM | 











Learn SAP on your system without installing SAP with SAP Visual's Training Simulator pack consisting of 1300+ sap simulators useful for beginners and professionals to learn all SAP modules. SAP is the acronym for Systems, Applications and Products in Data Processing. It was started in 1972 by
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/BCPdibcaWWGCw7s1QI4ny-lBVTs/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/BCPdibcaWWGCw7s1QI4ny-lBVTs/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/BCPdibcaWWGCw7s1QI4ny-lBVTs/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/BCPdibcaWWGCw7s1QI4ny-lBVTs/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2012/01/download-sap-training-simulators.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk8BRn86eSp7ImA9WhRVEUU.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-1252332701412378654</id><published>2011-12-22T23:01:00.001+05:30</published><updated>2012-01-10T14:10:57.111+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-10T14:10:57.111+05:30</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="How to...." /><title>How to Find SAP Objects in Requests &amp; Tasks</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/1252332701412378654/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2011/12/how-to-find-sap-objects-in-requests.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/1252332701412378654?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/1252332701412378654?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/-Rr6Cnj1onA/how-to-find-sap-objects-in-requests.html" title="How to Find SAP Objects in Requests &amp; Tasks" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html"> This program searches for objects in requests and tasks. You can specify the objects in the selection screen. Some object types used frequently are already listed, you only need to enter the name of the object itself (generically if you want). You can enter other object types yourself. You can restrict the requests/tasks by entering, for example, the number of the request, the owner, date 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/K5FhWORci2EQvN-fv-YtcqA-d-Y/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/K5FhWORci2EQvN-fv-YtcqA-d-Y/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/K5FhWORci2EQvN-fv-YtcqA-d-Y/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/K5FhWORci2EQvN-fv-YtcqA-d-Y/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2011/12/how-to-find-sap-objects-in-requests.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk8BRn86fSp7ImA9WhRVEUU.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-1270080015662311134</id><published>2011-12-22T22:59:00.001+05:30</published><updated>2012-01-10T14:10:57.115+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-10T14:10:57.115+05:30</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="How to...." /><title>How to Troubleshoot Mapping Error: JCO Communication Failure</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/1270080015662311134/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2011/12/how-to-troubleshoot-mapping-error-jco.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/1270080015662311134?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/1270080015662311134?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/EZ6QLNbhd-I/how-to-troubleshoot-mapping-error-jco.html" title="How to Troubleshoot Mapping Error: JCO Communication Failure" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html"> Sympton • In transaction code SMQ2, you received "XI Error JCO_COMMUNICATION_FAILURE.MAPPING: Queue error".• When executing the RFC test connection on AI_RUNTIME_JCOSERVER, AI_VALIDATION_JCOSERVER, LCRSAPRFC and SAPSLDAPI, you received error " ERROR: program AI_RUNTIME_SID not registered".   Cause At first, go for the logs file. From there, you'll find the specific root cause of the error. 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ektqJbSC5gwusp8i0QEKtyqJV8k/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ektqJbSC5gwusp8i0QEKtyqJV8k/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ektqJbSC5gwusp8i0QEKtyqJV8k/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ektqJbSC5gwusp8i0QEKtyqJV8k/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2011/12/how-to-troubleshoot-mapping-error-jco.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk8BRnw4fSp7ImA9WhRVEUU.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-8621516734849120965</id><published>2011-12-22T22:57:00.001+05:30</published><updated>2012-01-10T14:10:57.235+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-10T14:10:57.235+05:30</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="How to...." /><title>How to Delete Short Dumps from the SNAP Table</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/8621516734849120965/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2011/12/how-to-delete-short-dumps-from-snap.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/8621516734849120965?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/8621516734849120965?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/ZCrvED6Q26g/how-to-delete-short-dumps-from-snap.html" title="How to Delete Short Dumps from the SNAP Table" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html"> There are different ways of deleting short dumps from the SNAP table. However, before you delete them, you must analyze the cause of the short dump using transaction code ST22. If the issue related to short dumps is resolved, you can proceed to remove the short dumps before they all filling up the hard disk of your system. Here are the several ways to delete the short dumps:   1. Dump analysis: 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/q7FEGJ4_VWYkZ8YrfIYMHEg7QMI/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/q7FEGJ4_VWYkZ8YrfIYMHEg7QMI/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/q7FEGJ4_VWYkZ8YrfIYMHEg7QMI/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/q7FEGJ4_VWYkZ8YrfIYMHEg7QMI/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2011/12/how-to-delete-short-dumps-from-snap.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk8BRnw7eCp7ImA9WhRVEUU.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-5183750119575833757</id><published>2011-12-22T22:56:00.001+05:30</published><updated>2012-01-10T14:10:57.200+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-10T14:10:57.200+05:30</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="How to...." /><title>How to Lock &amp; Unlock Whole SAP System</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/5183750119575833757/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2011/12/how-to-lock-unlock-whole-sap-system.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/5183750119575833757?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/5183750119575833757?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/CngiWN8d1HU/how-to-lock-unlock-whole-sap-system.html" title="How to Lock &amp; Unlock Whole SAP System" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html"> You can lock and unlock whole SAP system using command prompt. This example is tested in UNIX and Linux environment. Please use adm user when executing the command.   • To lock the whole SAP system execute this command:       &amp;gt; tp locksys  pf=/usr/sap/trans/bin/TP_DOMAIN_.PFL          initial value of NLS_LANG: 'AMERICAN_AMERICA.UTF8'     This is tp version 372.05.14 (release 700, unicode 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/kTtfM9EnGvSBFZMq56dg8kgEFI4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/kTtfM9EnGvSBFZMq56dg8kgEFI4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/kTtfM9EnGvSBFZMq56dg8kgEFI4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/kTtfM9EnGvSBFZMq56dg8kgEFI4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2011/12/how-to-lock-unlock-whole-sap-system.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk8BRn8zeip7ImA9WhRVEUU.&quot;"><id>tag:blogger.com,1999:blog-516732954887332551.post-4436082715811226906</id><published>2011-12-22T22:52:00.001+05:30</published><updated>2012-01-10T14:10:57.182+05:30</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-10T14:10:57.182+05:30</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="How to...." /><title>How to Configure RFC Destinations in ABAP &amp; JAVA Environments</title><link rel="replies" type="application/atom+xml" href="http://sapbasis-security.blogspot.com/feeds/4436082715811226906/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://sapbasis-security.blogspot.com/2011/12/how-to-configure-rfc-destinations-in.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/4436082715811226906?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/516732954887332551/posts/default/4436082715811226906?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/qxrf/~3/hyap-I8hY-M/how-to-configure-rfc-destinations-in.html" title="How to Configure RFC Destinations in ABAP &amp; JAVA Environments" /><author><name>~SAP Consultant~</name><uri>http://www.blogger.com/profile/09291927154376738176</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="http://bp1.blogger.com/_h9NvDP-YuTA/R-xYEc2OcfI/AAAAAAAAAAU/XjufUqfFpFs/S220/SAP4.bmp" /></author><thr:total>0</thr:total><content type="html"> You need to create the following RFC destinations with both transaction SM59 (ABAP) and the Visual Administrator (Java).  AI_RUNTIME_JCOSERVER Points from the Integration Server to the mapping runtime. The program ID corresponds to the entry under JCo RFC provider for the J2EE Engine (used for the mapping runtime, value mapping, and the exchange profile).   AI_DIRECTORY_JCOSERVER Points from the
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/m2kWTCZVtYTJjMFCKSu0s03mFws/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/m2kWTCZVtYTJjMFCKSu0s03mFws/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/m2kWTCZVtYTJjMFCKSu0s03mFws/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/m2kWTCZVtYTJjMFCKSu0s03mFws/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;</content><feedburner:origLink>http://sapbasis-security.blogspot.com/2011/12/how-to-configure-rfc-destinations-in.html</feedburner:origLink></entry></feed>

