Could you check whether the tabel GENSETM is present at the database level ?
This table is used by for the SGEN process.
Also connect to the SAP system and check whether the table is present in the SAP.
Regards
RB
Could you check whether the tabel GENSETM is present at the database level ?
This table is used by for the SGEN process.
Also connect to the SAP system and check whether the table is present in the SAP.
Regards
RB
in se16 Not database tale exist for table GENSETM
Did you check other notes what i mentioned earlier ?
Also ckech :
1633118 - SGEN deletes GENSETM when restarting
best regards
ashish
Got this going , went into se11 and Activated table GENSETM
Got this going , went into se11 and Activated table GENSETM
Hi All,
Thanks for your help my issue was logging in the system for the first time using the GUI. I have managed to login using SAP* with default password and I can now add users into SAP system.
Regards,
Macdonald
Hi Miral,
I know the problem is already solved by other means, but you could have solved the issue by other means...
As your CI and DI has the same instance number and they are running locally on each cluster node you could have defined STMS with virtual ASCS hostname but, instead of ASCS system number, with CI (or DI) system number. This is to say, instead of ASCS:01 you could have defined with ASCS:00.
Regards,
Nuno Raposo
Yes Marius, I have rebooted the entire server as well but the problem still persists. Could there be problem with the hard drive as faulty? Or what could be the the potential problem.
It seems pretty much sure that the problem is not at SAP application end but on the OS or hard disk end.
Regards,
Sourabh Majumdar
Yes i agree with that, are both SAPserviceSID and sidadm part of the administrator group ?
as a test can you make the share full rights to everyone also the security on the hdd and try again ?
Yes, both the users are part of Administrator group and Everyone has also been given full rights both to HDD and saploc.
Regards,
Sourabh Majumdar
Please try the following
Scenario 3: SAP does not start at all: no message server and no dispatcher
Symptoms
The message server and the dispatcher do not start at all in the SAP MMC.
The following error when trying to view the developer traces within the SAP MMC: The network path was not found.
No new developer traces written to disk (under the “work” directory.)
Problem Analysis
The network shares “saploc” and “sapmnt” do not exist. That explains the “network path not found” message when attempting to view the developer traces within the SAP MMC.
Solution
Re-create the “saploc” and “sapmnt” network shares. Both need to be created on the \usr\sap directory.
source : http://sapbasisnotes.blogspot.de/2009/05/sap-startup-problems-in-windows.html
I want to update java stack in Netweaver PI 7.4 installed system. Current Java VM version is 1.6.0_43
I believe you want to upgrade the SAP J2EE stack upgrade.
Current Java VM version is 1.6.0_43
This is the JVM you have on the system and this is not the J2EE version.
use these links to find the present system information
http://hostname:5NN00/monitoring/SystemInfo
http://hostname:5NN00/monitoring/ComponentInfo
Refer to this document to know how to create a stack file and download the files
http://scn.sap.com/docs/DOC-26069
Regards
RB
Hi Amol
What is the Size of the DB? in windows 2008 have you disable the UAC?
Regards
Sriram
Hello Sriram,
Size of db is approx 150GB and UAC is not disbled.
Thanks
Amol
Hi Amol
In SAP installation you must disable the firewall & UAC
In place backup /restore you can move the database by using the deattach & attach method.
1. Stop the SAP application
2. Kindly refer the you tube video http://www.youtube.com/watch?v=gLMPAnSHSwQ
and Microsoft link http://support.microsoft.com/kb/224071
Regards
Sriram
Hello Sriram,
We are in process of upgrading hardware, we have purchased new hardware for this activity.
We are not disturbing our current setup until we complete backup restore activity.
Also we are not using detach/ attach method for backup restore.
We are simply making use of Tape drive for backup restore as i said above.
Regards,
Amol
Client copy from 04.12.2013 18:02:27
System ID............................ EH6
Target client........................ 900
R/3 Release.......................... 731
Basis Support Package...............SAPKB73102
Host................................. BSLHYDSAP
Start in background............. .....X
User................................. SAP*
Parameter
Source client........................ 000
Source client user masters............000
Copier profile:.......................SAP_ALL
Table selection
Customizing data .....................X
With application data................ X
Initialize and recreate......... X
Change documents are not copied
Start analysis of system 18:02:27
Error: Table /1FB/MD___M80001 error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M80001 does not exist
Error: Table /1FB/MD___M80002 error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M80002 does not exist
Error: Table /1FB/MD___M80003 error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M80003 does not exist
Error: Table /1FB/MD___M80004 error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M80004 does not exist
Error: Table /1FB/MD___M80005 error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M80005 does not exist
Error: Table /1FB/MD___M80006 error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M80007 does not exist
Error: Table /1FB/MD___M80008 error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M80008 does not exist
Error: Table /1FB/MD___M80009 error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M80009 does not exist
Error: Table /1FB/MD___M8000A error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M8000A does not exist
Error: Table /1FB/MD___M8000B error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M8000B does not exist
Error: Table /1FB/MD___M8000C error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M8000C does not exist
Error: Table /1FB/MD___M8000D error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M8000D does not exist
Error: Table /1FB/MD___M8000E error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M8000E does not exist
Error: Table /1FB/MD___M8000F error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M8000F does not exist
Error: Table /1FB/MD___M8000G error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M8000G does not exist
Error: Table /1FB/MD___M8000H error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M8000H does not exist
Error: Table /1FB/MD___M8000I error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M8000I does not exist
Error: Table /1FB/MD___M8000J error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M8000J does not exist
Error: Table /1FB/MD___M8000K error in DDIC - Check table with SE14
Could not generate the data object; the type /1FB/ MD___M8000K does not exist
Error: Table /1FB/MD___M8000L error in DDIC - Check table with SE14
Table BSEC is copied with cluster RFBLG, not explicitly
Active Option: AUTO_MAIL
Table Ins. Del. Upd. Func. kByte Time[sec] Time
You cannot use the RFC/server group parallel_generators
Start of post-processing by application exits 01:39:04
please reply ASAP client copy is hanged in between.
regards,
Ashish