Transporter allocation
I want to assign my transporter to a sale order so i can get details like which transporter allocate to which sale order.
I want to generate report also on that transporter, sale order which are already process or are in process in plant.
solution 1 : you can copy the reference list to manual percentages using copy package or another logic ,and ask user to modify manual adujistments and always consider manual adjustments for allocation .
solution 2 : create set of accounts and maintain these set of accounts as required. Ie if manual percentage is zero then take value from reference list . For this you might need to create separaate logic file. or maintain a hidden sheet in the template which you are providing user to enter manual percentages . In the hidden sheet you have to incorparate logic using excelAnd then use these set of accounts in allocation .
In both cases you need to do data preparation for driver accounts before using those in allocation.
Similar Messages
-
SEM-BPS: Transporting allocations
Hi,
I have used UPC_TRANSPORT_BPS_ALL to transport a planning function (Allocation) that contains several parameter groups. When going to target system I see the transported parameter groups but cannot process these. I get error message about missing consolidation methods. When I take a look at table e.g. ucf001c I see these parameter groups in source system but not in target system. This table is one of the consolidation methods. Does someone know is there any specific trick to transport planning functions for allocations?
Thanks!
Br
JHello,
I use for transport BPS0 instead or the report you have used.
I have developed Allocations (e. g. yesterday) and have transported it also. I had no problems, can execute it and I also had never these kind of error message.
One thing: Allocation is a BCS-Function and consolidation groups are BCS groups. I guess there must be something wrong in your system, because BPS allocation wants to check BCS customising, which does not make any sense here.
regards
Eckhard Lewin -
Stock Transport Order Allocation
Greetings,
I have created a new PO/STO type, ZRIC which is essentially a copy of type UB, the only change is that this allows for transfer of finished goods materials within the same plant between different storage locations. We have active storage locations where we pick from and virtual storage locations and so we needed a mechanism to transfer stock between them. We are created the STO via a PO in ME21n and using the SD delivery NL to fill the STO, I would like to know how I can restrict the allocation of goods to fill the delivery for this type of STO. I would like to have rule/exit/config where I can define which storage locations can be used to fill the deliveries created from my new STO PO. Since my active pick sloc is under the same plant as my virtual SLOC's I need to be precise. Any help will be rewarded quickly.
Thank you!Hi RS
1) Receiving Plant can be maintained as a customer with suitable Sales Area. Since customer is available as a characteristic in field catalogue, you can use the same. Alternately, you need to extend the structure (As Michael has advised). This is quite common requirement and your development colleagues will be able to help you.
2) Key figure will remain AMENGE irrespective of whether it is Sales Order or STO.
Thanks,
Prasun -
Transportation of Allocation Cycles
Hi all,
We are in the on-going support phase. Now there is a new requirement for alloaction of expenses. We will be using distribution cycles. Needed to know the following:
1) Since it is not part of BBP, would it constitute a Change request?
2) Are distribution cycles transported using a transport request or are they directly created in production? What is the best practice in this case?
Regards,
SangeetaHi,
1) Since it is not part of BBP, would it constitute a Change request?
In my opinion you could propose the two options, allthough in theory, a new costs distribution requirement is something very common, therefore I would prefer not consider a change request, but I would speak with the customer about the dificulty...
2) Are distribution cycles transported using a transport request or are they directly created in production? What is the best practice in this case?
It is much better to use requests, you willl be able to test the diferent cycles in other environments before. And later on, you will not do mistakes in production.
Regards -
Adding new field to product allocation catalog?
We are configuring product allocations in SCM 7.0 and have a requirement to add a new field to the standard field catalog for the allocations check. We have followed the procedure outlined by SAP to add our new field to the structure /SAPAPO/KOMGOZ, add the field to the field catalog, and copied the source code to ERP.
The issue that we are having is that new custom field that we added to the field catalog is not being populated when we execute /SAPAPO/ATPQ_PAREA_K - Characteristics Combinations from Planning Area. The product allocations group that is being used in /SAPAPO/ATPQ_PAREA_K has three characteristics. The first two which are SAP provided fields are being populated correctly, but the last custom field we added to the field catalog is not. It is just blank.
Is there a step that we missed during the configuation. We are only using this field for the product allocations check (we do not use Rules Based ATP).Hi Arnel,
I was expecting with examples but anyway.
consider the examples of your CVC
Country Region brand SO DV DC mat plant etc...
now you want to first get confirmation on SO and DV , Prd allo group with these 2 characteristics
same goes for all other combinations.
now if you want to go with Either Or /And.. decides if you need to go with one product allocation procedure with many prod allocation group /or/ a sequence product allocation procedure.
Its very straight forward as such... if you come up with examples, i can give better details.
Looking at point 3 it looks like you want to go with 'OR' so you will have to go with sequence.
(tcode: /SAPAPO/ATPCQ_GENER)- is to check the customizing, sometime you might move the Prod allocation from dev system and just to make sure there is no issue in transport /missing config.. it will check with transaction code. I don't think you have to run this every time. After every transport..may be you have too as a caution check.
Imp: just to check @ different levels i dont think you will have to create different planning area. If all the characteristics on which you want to (combinations) is available in one planning area , you should be good with one planning area only.
Hope this is helpful. I would suggest to follow what we have discussed so far and then you can create another message after the configuration/approach you finalized with new issues/concerns you will be facing.
If issue are really bothering you much, you can reach out to me directly. Let me know
Pravin M -
Cache Memory Allocator \ Short Term Memory Allocator Issues
Hi all
I have a number of identically configured (High School) Servers which are giving me the same memory errors (some more frequently than others) and I've run out of ideas.
They are all HP Proliant DL360 G6 Servers, NetWare 6.5 sp8 with eDir 8.8 sp5.
The error messages are :
"Cache memory allocator out of available memory." followed by "Short term memory allocator is out of memory. xxx attempts to get more memory failed. request size in bytes xxxxxxxx from Module SWEEP.NLM"
The module referred to is always "SWEEP.NLM" (Sophos Anti-virus). A Server reset solves the problem but it is normally back within a month.
I've posted below a config.txt and segstats.txt from one of the servers.
I would be grateful if someone could help me with this as it's now becoming a 'headache'.
Cheers
Neil Hughes
*** Memory Pool Configuration for : KLDSRV1
Time and date : 10:34:44 AM 01/18/2012
Server version : NetWare 6.5 Support Pack 8
Server uptime : 32d 20h 00m 00s
SEG.NLM version : v1.72
0xFFFFFFFF --------------------------------------------------------------
| Kernel Reserved Space |
| |
| Size : 180,355,071 bytes (172.0 MB) |
| |
0xF5400000 --------------------------------------------------------------
| User Address Space (L!=P) |
| |
| User Pool Size : 884,998,144 bytes (844.0 MB) |
| High Water Mark : 2,936,012,800 bytes (2.73 GB) |
| |
0xC0800000 --------------------------------------------------------------
| Virtual Memory Cache Pool (L!=P) |
| |
| VM Pool Size : 1,082,130,432 bytes (1.01 GB) |
| Available : 1,049,260,032 bytes (1000.7 MB) |
| Total VM Pages : 1,047,080,960 bytes (998.6 MB) |
| Free Clean VM : 1,025,097,728 bytes (977.6 MB) |
| Free Cache VM : 21,983,232 bytes (21.0 MB) |
| Total LP Pages : 0 bytes (0 KB) |
| Free Clean LP : 0 bytes (0 KB) |
| Free Cache LP : 0 bytes (0 KB) |
| Free Dirty : 0 bytes (0 KB) |
| VM Pages In Use : 2,179,072 bytes (2.1 MB) |
| NLM Memory In Use : 1,066,545,152 bytes (1017.1 MB) |
| NLM/VM Memory : 1,050,394,624 bytes (1001.7 MB) |
| Largest Segment : 16,240,640 bytes (15.5 MB) |
| High Water Mark : 1,535,295,488 bytes (1.43 GB) |
| |
0x80000000 --------------------------------------------------------------
| File System Cache Pool (L==P or L!=P) |
| |
| FS Pool Size : 2,141,048,832 bytes (1.99 GB) |
| Available : 252,231,680 bytes (240.5 MB) |
| Largest Segment : 10,547,200 bytes (10.1 MB) |
| |
| NSS Memory (85%) : 1,043,554,304 bytes (995.2 MB) |
| NSS (avail cache) : 958,324,736 bytes (913.9 MB) |
| |
0x00623000 --------------------------------------------------------------
| DOS / SERVER.NLM |
| |
| Size : 6,434,816 bytes (6.1 MB) |
| |
0x00000000 --------------------------------------------------------------
Top 6 Memory Consuming NLMs
NLM Name Version Date Total NLM Memory
================================================== ==============================
1. DS.NLM 20219.15 12 May 2009 242,957,527 bytes (231.7 MB)
2. NSS.NLM 3.27.03 7 Jun 2010 225,471,568 bytes (215.0 MB)
3. SERVER.NLM 5.70.08 3 Oct 2008 197,615,392 bytes (188.5 MB)
4. SWEEP.NLM 4.73 1 Dec 2011 104,793,570 bytes (99.9 MB)
5. DBSRV6.NLM 6.00.04 16 May 2001 38,735,938 bytes (36.9 MB)
6. XMGR.NLM 27610.01.01 30 Mar 2009 32,184,593 bytes (30.7 MB)
Logical Memory Summary Information
================================================== ==============================
File System Cache Information
FS Cache Free : 63,897,600 bytes (60.9 MB)
FS Cache Fragmented : 188,334,080 bytes (179.6 MB)
FS Cache Largest Segment : 10,547,200 bytes (10.1 MB)
Logical System Cache Information
LS Cache Free : 138,153,984 bytes (131.8 MB)
LS Cache Fragmented : 364,015,616 bytes (347.2 MB)
LS Cache Uninitialized : 333,455,360 bytes (318.0 MB)
LS Cache Largest Segment : 16,240,640 bytes (15.5 MB)
LS Cache Largest Position : 34490000
Summary Statistics
Total Free : 202,051,584 bytes (192.7 MB)
Total Fragmented : 552,349,696 bytes (526.8 MB)
Highest Physical Address : DF62E000
User Space : 1,065,353,216 bytes (1016.0 MB)
User Space (High Water Mark) : 2,936,012,800 bytes (2.73 GB)
NLM Memory (High Water Mark) : 1,535,295,488 bytes (1.43 GB)
Kernel Address Space In Use : 2,475,212,800 bytes (2.31 GB)
Available Kernel Address Space : 754,401,280 bytes (719.5 MB)
Memory Summary Screen (.ms)
================================================== ==============================
KNOWN MEMORY Bytes Pages Bytes Pages
Server: 3747295616 914867 Video: 8192 2
Dos: 111232 27 Other: 131072 32
FS CACHE KERNEL NLM MEMORY
Original: 3743006720 913820 Code: 48136192 11752
Current: 252231680 61580 Data: 28098560 6860
Dirty: 0 0 Sh Code: 40960 10
Largest seg: 10547200 2575 Sh Data: 20480 5
Non-Movable: 0 0 Help: 172032 42
Other: 1890455552 461537 Message: 1249280 305
Avail NSS: 958328832 233967 Alloc L!=P: 957685760 233810
Movable: 8192 2 Alloc L==P: 14991360 3660
Total: 1050394624 256444
VM SYSTEM
Free clean VM: 1025097728 250268
Free clean LP: 0 0
Free cache VM: 21983232 5367
Free cache LP: 0 0
Free dirty: 0 0
In use: 2179072 532
Total: 1049260032 256167
Memory Configuration (set parameters)
================================================== ==============================
Auto Tune Server Memory = OFF
File Cache Maximum Size = 2147483648
File Service Memory Optimization = 1
Logical Space Compression = 1
Garbage Collection Interval = 299.9 seconds
VM Garbage Collector Period = 300.0 seconds
server -u<number> = 884998144
NSS Configuration File:
C:\NWSERVER\NSSSTART.CFG
/AllocAheadBlks=0
/MinBufferCacheSize=20000
/MinOSBufferCacheSize=20000
/CacheBalanceMaxBuffersPerSession=20000
/NameCacheSize=200000
/AuthCacheSize=20000
/NumWorkToDos=100
/FileFlushTimer=10
/BufferFlushTimer=10
/ClosedFileCacheSize=100000
/CacheBalance=85
DS Configuration File:
SYS:\_NETWARE\_NDSDB.INI
preallocatecache=true
cache=200000000
Server High/Low Water Mark Values
================================================== ==============================
NLM Memory High Water Mark = 1,535,295,488 bytes
File System High Water Mark = 435,727 bytes
User Space Information:
User Space High Water Mark = 683,339,776 bytes
Committed Pages High Water Mark = 91 pages
Mapped VM Pages High Water Mark = 5,870 pages
Reserved Pages High Water Mark = 692,325 pages
Swapped Pages High Water Mark = 5,710 pages
Available Low Water Mark = 882,774,016
ESM Memory High Water Mark = 949 pages
Novell File Server Configuration Report For Server: KLDSRV1
Novell File Server Configuration Report Created: Wed, Jan 18, 2012 11:15 am
Novell File Server Configuration Report. [Produced by CONFIG.NLM v3.10.17]
Novell NetWare 5.70.08 October 3, 2008
(C) Copyright 1983-2008 Novell Inc. All Rights Reserved.
Server name...............: KLDSRV1
OS Version................: v5.70
OS revision number........: 8
Product Version...........: v6.50
Product Revision Number...: 8
Server Up Time(D:H:M:Sec).: 32:20:51:12
Serial number.............: XXXXXXXX
Internal Net. Addr........: 00000000h
Security Restriction Level: 1
SFT Level.................: 2
Engine Type...............: NATIVE
TTS Level.................: 1
Total Server memory.......: 3573.81 MB or 3747406848 Bytes
Processor speed rating....: 197582
Original cache buffers....: 913820
Current Cache Buffers.....: 292534
LRU Sitting Time(D:H:M:S).: 32:20:51:12
Current FSP's.............: 12
Current MP FSP's..........: 378
Current Receive Buffers...: 3000
Directory cache buffers...: 0
Workstations Connected....: 1136
Max Workstations Connected: 1528
Server language...........: ENGLISH (4)
Timesync active...........: Yes
Time is synchronized......: Yes
Total Processors..........: 4
Server DOS Country ID.....: 44
Server DOS Code Page......: 850
Boot Loader...............: DOS
Top of Modules List 312 Modules Loaded.
ACPIASL.NLM v1.05.16 Jan. 16, 2007 ACPI Architecture Services Layer for ACPI compliant systems
ACPICA.NLM v1.05.16 Jan. 16, 2007 ACPI Component Architecture for ACPI compliant systems
ACPICMGR.NLM v1.05.16 Jan. 16, 2007 ACPI Component Manager for ACPI compliant systems
ACPIDRV.PSM v1.05.19 Jan. 16, 2007 ACPI Platform Support Module for ACPI compliant systems
ACPIPWR.NLM v1.05.16 Jan. 16, 2007 ACPI Power Management Driver for ACPI compliant systems
AFREECON.NLM v5.00 Jul. 22, 2005 AdRem Free Remote Console (NCPE)
APACHE2.NLM v2.00.63 Apr. 25, 2008 Apache Web Server 2.0.63
APRLIB.NLM v0.09.17 Apr. 25, 2008 Apache Portability Runtime Library 0.9.17
AUTHLDAP.NLM v2.00.63 Apr. 25, 2008 Apache 2.0.63 LDAP Authentication Module
AUTHLDDN.NLM v1.00 Nov. 9, 2005 LdapDN Module
BROKER.NLM v3.00.12 Feb. 20, 2008 NDPS Broker
BSDSOCK.NLM v6.82.02 Dec. 23, 2009 Novell BSDSOCK Module
BTCPCOM.NLM v7.90 Jul. 9, 2003 BTCPCOM.NLM v7.90.000, Build 253
BTRIEVE.NLM v7.90 Mar. 21, 2001 BTRIEVE.NLM v7.90.000
CALNLM32.NLM v6.01.03 Aug. 26, 2008 NetWare NWCalls Runtime Library
CCS.NLM v27610.01.01 Mar. 30, 2009 Controlled Cryptography Services from Novell, Inc.
CDBE.NLM v6.01 Sep. 21, 2006 NetWare Configuration DB Engine
CDDVD.NSS v3.27.03 Jun. 7, 2010 NSS Loadable Storage System (LSS) for CD/UDF (Build 212 MP)
CERTLCM.NLM v28200902.26 Feb. 26, 2009 Novell SASL EXTERNAL Proxy LCM 2.8.2.0 20090226
CERTLSM.NLM v28200902.26 Feb. 26, 2009 Novell SASL EXTERNAL LSM 2.8.2.0 20090226
CHARSET.NLM v1.01 Jun. 4, 2003 Display Character Set Support For NetWare
CIOS.NLM v1.60 Feb. 12, 2008 Consolidated IO System
CLBACKUP.NLM v8.00 Sep. 22, 2010 NetWare Client Backup
CLBROWSE.NLM v8.00 Dec. 3, 2008 NetWare Client Browse
CLIB.NLM v5.90.15 Mar. 10, 2008 (Legacy) Standard C Runtime Library for NLMs
CLNNLM32.NLM v6.01.03 Aug. 26, 2008 NetWare NWClient Runtime Library
CLRESTOR.NLM v8.00 Mar. 31, 2009 NetWare Client Restore
CLXNLM32.NLM v6.01.03 Aug. 26, 2008 NetWare NWCLX Runtime Library
COMN.NSS v3.27.03 Jun. 7, 2010 NSS Common Support Layer (COMN) (Build 212 MP)
CONFIG.NLM v3.10.17 Feb. 12, 2008 NetWare Server Configuration Reader
CONLOG.NLM v3.01.02 Aug. 8, 2006 System Console Logger
CONNAUD.NLM v3.17 May. 10, 2005 NLS - Connection Metering
CONNMGR.NLM v5.60.01 Sep. 7, 2006 NetWare Connection Manager NLM
CPQBSSA.NLM v8.20 Jan. 29, 2009 HP Insight Management Base System Agent
CPQCI.NLM v1.06 Oct. 17, 2005 hp ProLiant iLO Management Interface Driver
CPQDASA.NLM v8.20.01 Feb. 24, 2009 HP Management Array Subsystem Agent
CPQHMMO.NLM v3.92 Jun. 10, 2003 Compaq HMMO Services Provider for NetWare
CPQHOST.NLM v8.20 Jan. 29, 2009 HP Insight Management Host Agent
CPQHTHSA.NLM v8.20 Jan. 29, 2009 HP Insight Management Health Agent
CPQNCSA.NLM v8.20 Dec. 11, 2008 HP Insight NIC Agent
CPQRISA.NLM v8.20 Jan. 29, 2009 HP Insight Management Remote Insight Agent
CPQSSSA.NLM v8.20.01 Feb. 24, 2009 HP Management Storage Box Subsystem Agent
CPQTHRSA.NLM v8.20 Jan. 29, 2009 HP Insight Management Threshold Agent
CPQWEBAG.NLM v8.20 Jan. 29, 2009 HP Web Based Management Agent
CPUCHECK.NLM v5.60.01 Dec. 6, 2007 NetWare Processor Checking Utility
CRLSM.NLM v2.08.01 Oct. 28, 2008 Challenge Response LSM v2.8.1.0
CSL.NLM v2.06.02 Jan. 13, 2000 NetWare Call Support Layer For NetWare
CSLIND.NLM v4.21 Dec. 7, 1999 TCPIP CSL INDEPENDENCE MODULE 7Dec99 7Dec99
CVAPPMGR.NLM v8.00 Nov. 22, 2010 AppManager
CVARCH.NLM v8.00 Nov. 10, 2010 Archive Library
CVD.NLM v8.00 Apr. 13, 2011 Communications Service
CVJOBCL.NLM v8.00 Nov. 10, 2010 Job Client
CVLIB.NLM v8.00 Apr. 13, 2011 Library for NetWare
CVLZOLIB.NLM v8.00 Dec. 3, 2008 LZO Compression Library
CVNETCHK.NLM v8.00 Dec. 3, 2008 Network Check
CVSIM.NLM v8.00 Dec. 3, 2008 Software Installation Manager
CVSMS.NLM v8.00 Sep. 28, 2009 NetWare SMS Interface
DBEXTF6.NLM v6.00.04 Sep. 12, 2000 Sybase Adaptive Server Anywhere External Library
DBNET6.NLM v1.45.02 Mar. 16, 2006 Debug Network IO Support
DBSRV6.NLM v6.00.04 May. 16, 2001 Sybase Adaptive Server Anywhere
DFSLIB.NLM v3.27.03 Jun. 7, 2010 DFS Common Library (Build 212 MP)
DHOST.NLM v10010.97 Sep. 18, 2006 Novell DHost Portability Interface 1.0.0 SMP
DIAG500.NLM v3.04.03 Oct. 31, 2007 Diagnostic/coredump utility for NetWare 6.x
DM.NLM v3.01.60 May. 21, 2008 Novell XTier Directory Manager
DMNDAP.NLM v3.01.60 May. 21, 2008 Novell XTier Directory Manager NDAP Provider
DPLSV386.NLM v1.15.03 Apr. 16, 2010 NetWare 6.x Distributed Print Library - DPLSV386
DPRPCNLM.NLM v3.00.17 Oct. 10, 2006 Novell NDPS RPC Library NLM
DS.NLM v20219.15 May. 12, 2009 Novell eDirectory Version 8.8 SP5 SMP
DSAPI.NLM v6.00.04 Jan. 27, 2006 NetWare NWNet Runtime Library
DSEVENT.NLM v6.01.03 Aug. 26, 2008 NetWare DSEvent Runtime Library
DSLOADER.NLM v20219.15 May. 12, 2009 Novell eDirectory Version 8.8.0 Loader SMP
DSLOG.NLM v20219.15 May. 12, 2009 DS Log for Novell eDirectory 8.8.0
DTS.NLM v3.01.05 Sep. 8, 2008 Transaction Server 3.1.0 - Netware
EHCIDRV.CAD v1.05 Feb. 26, 2008 Novell Universal Serial Bus EHCI driver
EPWDLSM.NLM v27000508.12 Aug. 12, 2005 Novell Enhanced Password LSM 2.7.0.0 20050812
ETADVLSM.NLM v27000508.03 Aug. 3, 2005 Novell Entrust LSM 2.7.0.0 20050803
ETHERTSM.NLM v3.90 Mar. 20, 2006 Novell Ethernet Topology Specific Module
EVENTMGR.NLM v3.01.60 May. 21, 2008 Novell XTier Event Manager
EVMGRC.NLM v8.00 Dec. 3, 2008 Event Manager Client
EXPIRES.NLM v2.00.63 Apr. 25, 2008 Apache 2.0.63 Expires Module
FATFS.NLM v1.24 Aug. 27, 2007 FAT Filesystem Module for NetWare
FILESYS.NLM v5.14 Apr. 16, 2008 NetWare File System NLM
FSBRWSE.NLM v8.00 Dec. 3, 2008 NetWare File System Browser
GALAXY.NLM v8.00 Dec. 3, 2008 Loader
GAMS.NLM v2.00.01 Sep. 2, 2008 Graded Authentication Management Service
HBNNSP.NLM v3.01.60 May. 21, 2008 Novell XTier GetHostByName Name Service Provider
HEADERS.NLM v2.00.63 Apr. 25, 2008 Apache 2.0.63 Headers Module
HOSTMIB.NLM v5.03.01 Dec. 1, 2006 NetWare 5.x/6.x Host Resources MIB
HPASMXL.NLM v1.14 Jan. 25, 2009 HP ProLiant Embedded Health Driver
HPQCISS.HAM v1.16.01 Mar. 3, 2009 HP SAS/SATA Unified RAID driver
HTTPSTK.NLM v4.03 Sep. 4, 2008 Novell Small Http Interface
HWDETECT.NLM v1.19.05 Feb. 20, 2003 Novell Hardware Insertion/Removal Detection
IDEATA.HAM v4.34 May. 5, 2007 Novell IDE/ATA/ATAPI/SATA Host Adapter Module
IFACE.NLM v7.05.04 Dec. 1, 2011 SAV Interface for NetWare
IFOLDER.NLM v2.04 Feb. 19, 2007 ifolder
IFOLDERU.NLM v2.04 Feb. 19, 2007 ifolderu
IMGSERV.NLM v7.00 Jan. 12, 2009 ZENworks Imaging Server
IPCTL.NLM v3.01.60 May. 21, 2008 Novell XTier Transport Layer
IPMCFG.NLM v1.01.16 Oct. 22, 2005 Web Interface for IP Address Management
IPMGMT.NLM v1.03.01 May. 29, 2007 TCPIP - NetWare IP Address Management
IPPSRVR.NLM v4.02.02 Jun. 16, 2010 Novell iPrint Server
JAVA.NLM v1.43 Oct. 16, 2008 java.nlm (based on 1.4.2_18) Build 08101613
JNCPV2.NLM v1.10 Nov. 13, 2003 Native Wrapper Java Class Libraries for NetWare
JNET.NLM v1.43 Oct. 16, 2008 Java jnet (based on 1.4.2_18)
JSMSG.NLM v3.27.03 Jun. 7, 2010 Jetstream Message Layer (Build 212 MP)
JSOCK.NLM v1.43 Oct. 16, 2008 Support For Java Sockets (loader)
JSOCK6X.NLM v1.43 Oct. 16, 2008 NetWare 6.x Support For Java Sockets (JDK 1.4.2)
JSTCP.NLM v3.27.03 Jun. 7, 2010 Jetstream TCP Transport Layer (Build 212 MP)
JVM.NLM v1.43 Oct. 16, 2008 Java Hotspot 1.4.2_18 Interpreter
JVMLIB.NLM v1.43 Oct. 16, 2008 Java jvmlib (based on 1.4.2_18)
KEYB.NLM v2.10 Jul. 26, 2001 NetWare National Keyboard Support
LANGMANI.NLM v10212.02 Mar. 10, 2009 Novell Cross-Platform Language Manager
LBURP.NLM v20216.02 Mar. 10, 2009 LDAP Bulkload Update/Replication Protocol service extension for Novell eDirectory 8.8
LCMCIFS2.NLM v2.00.09 Sep. 14, 2007 Windows Native File Access Login Methods (Build 91 SP)
LCMMD5.NLM v28000806.23 Jun. 23, 2008 Novell SASL DIGEST-MD5 Proxy LCM 2.8.0.0 20080623
LDAPSDK.NLM v3.05.02 Apr. 12, 2009 LDAP SDK Library (Clib version)
LDAPXS.NLM v3.05.01 Apr. 12, 2009 (Clib version)
LFS.NLM v5.12 Sep. 21, 2005 NetWare Logical File System NLM
LIB0.NLM v5.90.15 Mar. 10, 2008 Novell Ring 0 Library for NLMs
LIBC.NLM v9.00.05 Oct. 3, 2008 Standard C Runtime Library for NLMs [optimized, 7]
LIBCCLIB.NLM v6.00 Oct. 23, 2002 LibC to CLib Shim for NLMs [optimized, 0]
LIBCVCL.NLM v8.00 Dec. 3, 2008 Cryptography Library
LIBNICM.NLM v3.01.60 May. 21, 2008 Novell XTier Base Services
LIBNSS.NLM v3.27.03 Jun. 7, 2010 Generic Library used by NSS (Build 212 MP)
LIBPERL.NLM v5.00.05 Sep. 13, 2005 Perl 5.8.4 - Script Interpreter and Library
LIBXML2.NLM v2.06.26 Aug. 27, 2006 libxml2 2.6.26 (LIBC) - The XML C parser and toolkit of Gnome
LIBXTREG.NLM v3.01.60 May. 21, 2008 Novell XTier Base Services
LLDAPSDK.NLM v3.05.02 Apr. 12, 2009 LDAP SDK Library (LibC version)
LLDAPSSL.NLM v3.05.01 Apr. 12, 2009 NetWare SSL Library for LDAP SDK (LibC version)
LLDAPX.NLM v3.05.01 Apr. 12, 2009 NetWare Extension APIs for LDAP SDK (LibC version)
LOCNLM32.NLM v6.00.04 Nov. 29, 2005 NetWare NWLocale Runtime Library
LSAPI.NLM v5.02 Jan. 7, 2003 NLS LSAPI Library
LSL.MPM v5.70 Feb. 15, 2006 lsl Memory Protection Module
LSL.NLM v4.86 Feb. 2, 2006 Novell NetWare Link Support Layer
LSMAFP3.NLM v2.00.11 Sep. 14, 2007 Macintosh Native File Access Login Methods (Build 118 SP)
LSMCIFS2.NLM v2.00.07 Sep. 14, 2007 Windows Native File Access Login Methods (Build 103 SP)
LSMMD5.NLM v28000806.23 Jun. 23, 2008 Novell SASL DIGEST-MD5 LSM 2.8.0.0 20080623
MAL.NSS v3.27.03 Jun. 7, 2010 NSS Media Access Layer (MAL) (Build 212 MP)
MALHLP.NLM v3.27.03 Jun. 7, 2010 NSS Configure help messages (Build 212 MP)
MANAGE.NSS v3.27.03 Jun. 7, 2010 NSS Management Functions (Build 212 MP)
MASV.NLM v2.00.01 Sep. 2, 2008 Mandatory Access Control Service
MATHLIB.NLM v4.21 Oct. 14, 1999 NetWare Math Library Auto-Load Stub
MM.NLM v3.22.08 Apr. 24, 2009 ENG TEST - NetWare 6.5 Media Manager
MOD_IPP.NLM v1.00.04 Jun. 7, 2006 iPrint Module
MOD_JK.NLM v1.02.23 Apr. 25, 2008 Apache 2.0 plugin for Tomcat
MOD_XSRV.NLM v3.01.04 May. 21, 2008 Novell XTier Server (Apache2 Module)
MOMAPSNW.NLM v4.00 May. 7, 2010 4.0 Build: 492 NW FC AB 2010-05-07 NW
MONDATA.NLM v6.00 Jul. 18, 2003 NetWare 5.x/6.x Monitor MIB
MONITOR.NLM v12.02.02 Apr. 4, 2006 NetWare Console Monitor
MSM.NLM v4.12 Aug. 22, 2007 Novell Multi-Processor Media Support Module
N1000E.LAN v10.47 Oct. 6, 2007 HP NC-Series Intel N1E Ethernet driver
NBI.NLM v3.01.01 Jul. 13, 2007 NetWare Bus Interface
NCM.NLM v1.15.01 Oct. 20, 2004 Novell Configuration Manager
NCP.NLM v5.61.01 Sep. 30, 2008 NetWare Core Protocol (NCP) Engine
NCPIP.NLM v6.02.01 Sep. 30, 2008 NetWare NCP Services over IP
NCPL.NLM v3.01.60 May. 21, 2008 Novell XTier Base Services
NCPNLM32.NLM v6.01.03 Aug. 26, 2008 NetWare NWNCP Runtime Library
NDPSGW.NLM v4.01.02 Mar. 2, 2010 NDPS Gateway
NDPSM.NLM v3.03.02 May. 18, 2010 NDPS Manager
NDS4.NLM v3.01.60 Apr. 9, 2008 Novell XTier NDS4 Authentication Provider
NDSAUDIT.NLM v2.09 May. 22, 2003 Directory Services Audit
NDSIMON.NLM v20216.12 Apr. 15, 2009 NDS iMonitor 8.8 SP5
NEB.NLM v5.60 Sep. 27, 2004 Novell Event Bus
NETDB.MPM v5.70 Feb. 15, 2006 netdb Memory Protection Module
NETDB.NLM v4.11.05 Jan. 6, 2005 Network Database Access Module
NETLIB.NLM v6.50.22 Feb. 12, 2003 Novell TCPIP NETLIB Module
NETNLM32.NLM v6.01.03 Aug. 26, 2008 NetWare NWNet Runtime Library
NIAM.NLM v3.01.60 May. 21, 2008 Novell XTier Identity Manager
NICISDI.NLM v27610.01.01 Mar. 30, 2009 Security Domain Infrastructure
NILE.NLM v7.00.01 Aug. 20, 2007 Novell N/Ties NLM ("") Release Build with symbols
NIPPED.NLM v1.03.09 Jul. 11, 2006 NetWare 5.x, 6.x INF File Editing Library - NIPPED
NIPPZLIB.NLM v1.00.01 Nov. 28, 2005 General Purpose ZIP File Library for NetWare
NIRMAN.NLM v1.06.04 Sep. 18, 2007 TCPIP - NetWare Internetworking Remote Manager
NIT.NLM v5.90.15 Mar. 10, 2008 NetWare Interface Tools Library for NLMs
NLDAP.NLM v20219.14 May. 13, 2009 LDAP Agent for Novell eDirectory 8.8 SP5
NLMLIB.NLM v5.90.15 Mar. 10, 2008 Novell NLM Runtime Library
NLSADPT2.NLM v2.00 Sep. 9, 2003 NLS and Metering adapter for iManager 2.0 plugin
NLSAPI.NLM v5.02 Aug. 7, 2003 NLSAPI
NLSLRUP.NLM v4.01.07 May. 10, 2005 NLS - Usage Metering
NLSLSP.NLM v5.02 May. 25, 2005 NLS - License Service Provider
NLSMETER.NLM v3.43 May. 10, 2005 NLS - Software Usage Metering Database
NLSTRAP.NLM v5.02 Feb. 19, 2004 NetWare License Server Trap
NMAS.NLM v33200904.07 Apr. 7, 2009 Novell Modular Authentication Service 3.3.2.0 20090407
NMASGPXY.NLM v33200904.07 Apr. 7, 2009 NMAS Generic Proxy 3.3.2.0 20090407
NMASLDAP.NLM v33200904.07 Apr. 7, 2009 NMAS LDAP Extensions 3.3.2.0 20090407
NPKIAPI.NLM v3.33 Apr. 16, 2009 Public Key Infrastructure Services
NPKIT.NLM v3.33 Apr. 16, 2009 Public Key Infrastructure Services
NSCM.NLM v3.01.60 May. 21, 2008 Novell XTier Security Context Manager
NSNS.NLM v3.01.60 May. 21, 2008 Novell XTier Simple Name Service
NSPDNS.NLM v6.20.03 Sep. 8, 2003 NetWare Winsock 2.0 NSPDNS.NLM Name Service Providers
NSPNDS.NLM v6.20 Nov. 12, 2001 NetWare Winsock 2.0 NSPNDS.NLM Name Service Provider
NSPSLP.NLM v6.20.04 Dec. 6, 2007 NetWare Winsock 2.0 NSPSLP.NLM Name Service Provider
NSS.NLM v3.27.03 Jun. 7, 2010 NSS (Novell Storage Services) (Build 212 MP)
NSSIDK.NSS v3.27.03 Jun. 7, 2010 NSS Pool Configuration Manager (Build 212 MP)
NSSWIN.NLM v3.27.03 Jun. 7, 2010 NSS ASCI Window API Library (Build 212 MP)
NTFYDPOP.ENM v2.00.03 Feb. 26, 1999 Directed Pop-Up Delivery Method
NTFYLOG.ENM v2.00.03 May. 25, 1999 Log File Delivery Method
NTFYPOP.ENM v2.00.03 May. 21, 1999 Pop Up Delivery Method
NTFYRPC.ENM v2.00.03 Feb. 26, 1999 RPC Delivery Method
NTFYSPX.ENM v2.00.03 Feb. 26, 1999 SPX Delivery Method
NTFYSRVR.NLM v3.00.05 May. 10, 2005 NDPS Notification Server
NTFYWSOC.ENM v2.00.03 Feb. 26, 1999 Winsock Delivery Method
NTLS.NLM v20510.01 Mar. 11, 2009 NTLS 2.0.5.0 based on OpenSSL 0.9.7m
NWAIF103.NLM v7.94 Nov. 30, 2001 nwaif103.nlm v7.94, Build 251 ()
NWBSRVCM.NLM v7.90 Mar. 20, 2001 NWBSRVCM.NLM v7.90.000, Build 230
NWENC103.NLM v7.90 Feb. 24, 2001 NWENC103.NLM v7.90.000 (Text Encoding Conversion Library)
NWIDK.NLM v3.01.01 Sep. 19, 2003 CDWare Volume Module
NWKCFG.NLM v2.16 Jun. 24, 2005 NetWare Kernel Config NLM
NWMKDE.NLM v7.94 Dec. 11, 2001 NWMKDE.NLM v7.94.251.000
NWMON.NLM v1.20 Dec. 14, 2005 NetWare Monitoring Software
NWPA.NLM v3.21.02 Oct. 29, 2008 NetWare 6.5 NetWare Peripheral Architecture NLM
NWPALOAD.NLM v3.00 Jul. 10, 2000 NetWare 5 NWPA Load Utility
NWSA.NSS v3.27.03 Jun. 7, 2010 NSS NetWare Semantic Agent (NWSA) (Build 212 MP)
NWSNUT.NLM v7.00.01 Jul. 11, 2008 NetWare NLM Utility User Interface
NWTERMIO.NLM v1.00 Sep. 11, 2006 NetWare Terminal Emulation
NWTRAP.NLM v6.00.05 Jun. 6, 2005 NetWare 5.x/6.x Trap Monitor
NWUCMGR.NLM v1.05 Mar. 14, 2001 NWUCMGR.NLM v1.5 Build 230
NWUTIL.NLM v3.00.02 Aug. 20, 2007 Novell Utility Library NLM (_NW65[SP7]{""})
PARTAPI.NLM v2.00 Apr. 17, 2002 Partition APIs for NetWare 6.1
PDHCP.NLM v2.08 Oct. 20, 2003 Di-NIC Proxy DHCP Server
PKI.NLM v3.33 Apr. 16, 2009 Novell Certificate Server
PKIAPI.NLM v2.23.10 Nov. 20, 2004 Public Key Infrastructure Services
PMAP.NLM v2.01.04 Mar. 6, 2008 ZENworks Port Mapper Service
PMLODR.NLM v1.26 Oct. 7, 2005 PMLodr for NW65
PMPORTAL.NLM v2.16 Nov. 21, 2003 NetWare License Information Portal
POLIMGR.NLM v6.27 Nov. 3, 2005 NetWare License Policy Manager
PORTAL.NLM v4.03 Sep. 22, 2008 Novell Remote Manager NLM
PROCMODS.NLM v8.00 Nov. 5, 2010 PipeLine Procedure Module
PSVCS.NLM v251.00 Nov. 30, 2001 Portability Services
PVER500.NLM v3.00 Feb. 1, 2007 NetWare 6.XX Version Library
PWDLCM.NLM v28000806.23 Jun. 23, 2008 Novell Simple Password Proxy LCM 2.8.0.0 20080623
PWDLSM.NLM v28000806.23 Jun. 23, 2008 Novell Simple Password LSM 2.8.0.0 20080623
QUEUE.NLM v5.60 May. 24, 2001 NetWare Queue Services NLM
REGSRVR.NLM v3.00.06 May. 10, 2005 NDPS Service Registry
REQUESTR.NLM v5.90.15 Mar. 10, 2008 Novell NCP Requestor for NLMs
REWRITE.NLM v2.00.63 Apr. 25, 2008 Apache 2.0.63 Rewrite Module
RMANSRVR.NLM v3.07.02 Mar. 2, 2010 NDPS Resource Manager
ROLLCALL.NLM v5.00 Jul. 27, 1998 RollCall NLM (101, API 1.0)
ROTLOGS.NLM v2.00.63 Apr. 25, 2008 Apache 2.0.63 Log Rotation Utility for NetWare
SAL.NLM v20413.01 Mar. 25, 2009 Novell System Abstraction Layer Version 2.3.1
SASDFM.NLM v27610.01.01 Mar. 30, 2009 SAS Data Flow Manager
SASL.NLM v33200904.07 Apr. 7, 2009 Simple Authentication and Security Layer 3.3.2.0 20090407
SAVENGIN.NLM v3.27 Dec. 1, 2011 SAV Interface engine
SCSIHD.CDM v3.03.10 May. 30, 2008 Novell NetWare SCSI Fixed Disk Custom Device Module
SEG.NLM v1.72 Nov. 4, 2004 NetWare Memory Analyzer
SERVINST.NLM v5.00.13 Nov. 21, 2005 NetWare 5.x/6.x Instrumentation
SGUID.NLM v6.01 Sep. 27, 2002 NetWare GUID Services
SLP.MPM v5.70 Feb. 15, 2006 slp Memory Protection Module
SLP.NLM v2.13 Nov. 15, 2005 SERVICE LOCATION PROTOCOL (RFC2165/RFC2608)
SLPTCP.NLM v2.13 Nov. 15, 2005 SERVICE LOCATION TCP/UDP INTERFACE (RFC2165/RFC2608)
SMDR.NLM v6.58.01 Oct. 16, 2008 SMS - Storage Data Requestor
SMSUT.NLM v1.01.03 Jun. 26, 2008 SMS - Utility Library for NetWare 6.X
SNMP.MPM v5.70 Feb. 15, 2006 snmp Memory Protection Module
SNMP.NLM v4.18 Jul. 25, 2006 Netware 4.x/5.x/6.x SNMP Service
SPMDCLNT.NLM v33200904.07 Apr. 7, 2009 Novell SPM Client for DClient 3.3.2.0 20090407
STREAMS.MPM v5.70 Feb. 15, 2006 streams Memory Protection Module
STREAMS.NLM v6.00.06 May. 4, 2005 NetWare STREAMS PTF
SVCCOST.NLM v3.01.60 May. 21, 2008 Novell XTier Service Costing Module
SWEEP.NLM v4.73 Dec. 1, 2011 Sophos Anti-Virus User Interface
SYSCALLS.NLM v5.61 Aug. 2, 2007 NetWare Operating System Call and Marshalling Library
SYSLOG.NLM v6.05.03 Oct. 22, 2007 NetWare Logfile Daemon
TCP.NLM v6.82.06 Dec. 23, 2009 Novell TCP/IP Stack - Transport module (NULL encryption)
TCPIP.MPM v5.70 Feb. 15, 2006 tcpip Memory Protection Module
TCPIP.NLM v6.82.02 Sep. 30, 2009 Novell TCP/IP Stack - Network module (NULL encryption)
TCPSTATS.NLM v6.50.10 Jun. 20, 2003 Web Interface for Protocol Monitoring
TFTP.NLM v2.05.01 Jan. 15, 2008 ZENworks Preboot TFTP Server
THREADS.NLM v5.90.15 Mar. 10, 2008 Novell Threads Package for NLMs
TIMESYNC.NLM v6.61.01 Oct. 14, 2005 NetWare Time Synchronization Services
TLI.MPM v5.70 Feb. 15, 2006 tli Memory Protection Module
TLI.NLM v4.30.02 Dec. 19, 2000 NetWare Transport Level Interface Library
TSAFS.NLM v6.53.03 Oct. 16, 2008 SMS - File System Agent for NetWare 6.X
TSANDS.NLM v20215.04 Apr. 3, 2009 TSA for Novell eDirectory 7.x, 8.x
UHCIDRV.CAD v1.07 Feb. 26, 2008 Novell Universal Serial Bus UHCI driver
UNICODE.NLM v7.00 Oct. 26, 2004 NetWare Unicode Runtime Library (UniLib-based) [optimized]
USCLSM.NLM v27000507.14 Jul. 14, 2005 Novell Universal SmartCard LSM 2.7.0.0 20050714
USERLIB.NLM v5.60 Sep. 29, 2008 NetWare Operating System Function Library
UTILLDAP.NLM v2.00.63 Apr. 25, 2008 Apache 2.0.63 LDAP Authentication Module
UTILLDP2.NLM v1.00 Nov. 9, 2005 LdapDN Module
VDISK.NLM v1.00 Nov. 30, 2004 NetWare Virtual Disk
VERIFY.NLM v1.43 Oct. 16, 2008 Java verify (based on 1.4.2_18)
VLRPC.NLM v3.27.03 Jun. 7, 2010 DFS Volume Location Database (VLDB) RPC interface (Build 212 MP)
VMRPC.NLM v3.27.03 Jun. 7, 2010 DFS Volume Manager RPC interface (Build 212 MP)
VOLMN.NSS v3.27.03 Jun. 7, 2010 NSS Distributed Volume Manager (Build 212 MP)
VOLSMS.NLM v3.27.03 Jun. 7, 2010 NSS Distributed Volume Manager (Build 212 MP)
WS2_32.NLM v6.24.01 Feb. 14, 2008 NetWare Winsock 2.0 NLM
WSPIP.NLM v6.24 Dec. 4, 2007 NetWare Winsock Service 1.0 NLM for TCP and UDP
WSPSSL.NLM v6.26 Dec. 4, 2007 NetWare Winsock Service 1.0 NLM for SSL
X509ALSM.NLM v27000508.03 Aug. 3, 2005 Novell Advanced X.509 LSM 2.7.0.0 20050803
X509LSM.NLM v27000508.03 Aug. 3, 2005 Novell Simple X.509 LSM 2.7.0.0 20050803
XENGEXP.NLM v27610.01.01 Mar. 30, 2009 NICI Import Restricted XENG from Novell, Inc.
XENGNUL.NLM v27610.01.01 Mar. 30, 2009 NICI NULL XENG from Novell, Inc.
XENGUSC.NLM v27610.01.01 Mar. 30, 2009 NICI U.S./Worldwide XENG from Novell, Inc.
XI18N.NLM v10310.53 Aug. 2, 2005 Novell Cross-Platform Internationalization Package
XIM.XLM v27510.02.01 Aug. 25, 2008 Novell NICI Signed Loader
XMGR.NLM v27610.01.01 Mar. 30, 2009 NICI XMGR from Novell, Inc.
XNGAUSC.NLM v27610.01.01 Mar. 30, 2009 NICI U.S./Worldwide XMGR Assistant XENG from Novell, Inc.
XSRVNSP.NLM v3.01.60 May. 21, 2008 Novell XTier XSRVNSP Tree Name Service Provider
XSUP.NLM v27610.01.01 Mar. 30, 2009 NICI XSUP from Novell, Inc.
XTNCP.NLM v3.01.60 May. 21, 2008 Novell XTier NCP Session Layer Driver
XTUTIL.NLM v3.01.60 May. 21, 2008 Novell XTier Utility Functions
ZENIMGDS.NLM v7.00 Mar. 26, 2007 ZENworks Imaging DS Library
ZENPXE.NLM v7.00 Apr. 22, 2008 ZENworks Imaging PXE Library
ZENWS.NLM v1.00 Jul. 29, 2002 Zen Workstation Utility NLM
ZIP.NLM v1.43 Oct. 16, 2008 Java zip (based on 1.4.2_18)
ZLIB.NLM v1.01.04 Dec. 20, 2002 ZLIB 1.1.4 General Purpose Compression Library for NetWare
ZLSS.NSS v3.27.03 Jun. 7, 2010 NSS Journaled Storage System (ZLSS) (Build 212 MP)
End of Modules List 312 Modules Loaded.
Top of LAN Driver Configuration Listing
Signature.....: HardwareDriverMLID
CFG Version...: 1.15
Node Address..: 002655D01666
Board Number..: 1
Board Instance: 1
Media Type....: ETHERNET_II
MLID Version..: 10.47
Slot..........: 101
I/O...........: 5000h -> 501Fh
Memory........: FBFE0000h -> FBFFFFFFh
and FBFC0000h -> FBFC0FFFh
IRQ...........: 7
DMA...........: None
Logical Name..: N1000E_1_EII
Signature.....: HardwareDriverMLID
CFG Version...: 1.15
Node Address..: 002655D01667
Board Number..: 2
Board Instance: 2
Media Type....: ETHERNET_II
MLID Version..: 10.47
Slot..........: 102
I/O...........: 5020h -> 503Fh
Memory........: FBFA0000h -> FBFBFFFFh
and FBF80000h -> FBF80FFFh
IRQ...........: 11
DMA...........: None
Logical Name..: N1000E_2_EII
End of LAN Driver Configuration Listing
Top of Boot Drive Information
SERVER.EXE loaded from...........: C:\NWSERVER\
SERVER.EXE version...............: 1355757 bytes 10-03-2008 09:53am
Total Space on Drive.............: 2016 MB
Available Space..................: 1920 MB
End of Boot Drive Information
Top of Storage Device Configuration Information
Storage Device Summary:
0x0000 [V100-A100] USB UHCI Controller
0x0001 [V100-A101] USB UHCI Controller
0x0002 [V100-A102] USB UHCI Controller
0x0003 [V100-A103] USB UHCI Controller
0x0004 [V100-A104] USB EHCI Controller
0x0005 [V100-A105] USB UHCI Controller
0x0006 [V505-A0] HP SAS/SATA Unified RAID Driver
0x0007 [V505-A0-D0:0] HP LOGICAL VOLUME f/w:1.66
0x0008 DOS Partitioned Media
0x0019 [V505-A0-D0:0-PAA6BA] Free Partition Space
0x0009 [V505-A0-D0:0-P0] Big DOS; OS/2; Win95 Partition
0x000A [V505-A0-D0:0-P7F8] NSS Partition
0x000B [V505-A0-D0:0-P4678] NSS Partition
0x000C [V505-A0-D0:0-P1CD18] NSS Partition
0x000D [V505-A0-D0:0-P21B38] NSS Partition
0x000F [V505-A0-D0:0-P26B38] NSS Partition
0x0011 [V505-A0-D0:0-P2BB38] NSS Partition
0x0012 [V505-A0-D0:0-P30B38] Free Partition Space
0x0013 [V505-A0-D0:0-P353B8] NSS Partition
0x0014 [V505-A0-D0:0-P48C38] NSS Partition
0x0015 [V505-A0-D0:0-P612D8] NSS Partition
0x0016 [V505-A0-D0:0-P79978] NSS Partition
0x0017 [V505-A0-D0:0-P92018] NSS Partition
0x0018 [V505-A0-D0:0-PAA6B8] Free Partition Space
Storage Device Details:
[V100-A100] USB UHCI Controller
Media Manager object ID..: 0x0000
Media Manager Object Type: Adapter
Driver name..............: UHCIDRV.CAD
Assigned driver ID.......: 256
Adapter number...........: 256
Primary port address.....: 1000
Primary port length......: 18
Secondary port address...: Not used
Secondary port length....: Not used
Interrupt 0..............: 18
Interrupt 1..............: Not used
Slot.....................: 10027
DMA0.....................: Not used
DMA1.....................: Not used
Memory 0 address.........: Not used
Memory 0 length..........: Not used
Memory 1 address.........: Not used
Memory 1 length..........: Not used
[V100-A101] USB UHCI Controller
Media Manager object ID..: 0x0001
Media Manager Object Type: Adapter
Driver name..............: UHCIDRV.CAD
Assigned driver ID.......: 256
Adapter number...........: 257
Primary port address.....: 1020
Primary port length......: 18
Secondary port address...: Not used
Secondary port length....: Not used
Interrupt 0..............: 28
Interrupt 1..............: Not used
Slot.....................: 10028
DMA0.....................: Not used
DMA1.....................: Not used
Memory 0 address.........: Not used
Memory 0 length..........: Not used
Memory 1 address.........: Not used
Memory 1 length..........: Not used
[V100-A102] USB UHCI Controller
Media Manager object ID..: 0x0002
Media Manager Object Type: Adapter
Driver name..............: UHCIDRV.CAD
Assigned driver ID.......: 256
Adapter number...........: 258
Primary port address.....: 1040
Primary port length......: 18
Secondary port address...: Not used
Secondary port length....: Not used
Interrupt 0..............: 38
Interrupt 1..............: Not used
Slot.....................: 10029
DMA0.....................: Not used
DMA1.....................: Not used
Memory 0 address.........: Not used
Memory 0 length..........: Not used
Memory 1 address.........: Not used
Memory 1 length..........: Not used
[V100-A103] USB UHCI Controller
Media Manager object ID..: 0x0003
Media Manager Object Type: Adapter
Driver name..............: UHCIDRV.CAD
Assigned driver ID.......: 256
Adapter number...........: 259
Primary port address.....: 1060
Primary port length......: 18
Secondary port address...: Not used
Secondary port length....: Not used
Interrupt 0..............: 28
Interrupt 1..............: Not used
Slot.....................: 10030
DMA0.....................: Not used
DMA1.....................: Not used
Memory 0 address.........: Not used
Memory 0 length..........: Not used
Memory 1 address.........: Not used
Memory 1 length..........: Not used
[V100-A104] USB EHCI Controller
Media Manager object ID..: 0x0004
Media Manager Object Type: Adapter
Driver name..............: EHCIDRV.CAD
Assigned driver ID.......: 256
Adapter number...........: 260
Primary port address.....: Not used
Primary port length......: Not used
Secondary port address...: Not used
Secondary port length....: Not used
Interrupt 0..............: 18
Interrupt 1..............: Not used
Slot.....................: 10031
DMA0.....................: Not used
DMA1.....................: Not used
Memory 0 address.........: 0000
Memory 0 length..........: 006C
Memory 1 address.........: Not used
Memory 1 length..........: Not used
[V100-A105] USB UHCI Controller
Media Manager object ID..: 0x0005
Media Manager Object Type: Adapter
Driver name..............: UHCIDRV.CAD
Assigned driver ID.......: 256
Adapter number...........: 261
Primary port address.....: 3800
Primary port length......: 18
Secondary port address...: Not used
Secondary port length....: Not used
Interrupt 0..............: 38
Interrupt 1..............: Not used
Slot.....................: 10037
DMA0.....................: Not used
DMA1.....................: Not used
Memory 0 address.........: Not used
Memory 0 length..........: Not used
Memory 1 address.........: Not used
Memory 1 length..........: Not used
[V505-A0] HP SAS/SATA Unified RAID Driver
Media Manager object ID..: 0x0006
Media Manager Object Type: Adapter
Driver name..............: HPQCISS.HAM
Assigned driver ID.......: 1285
Adapter number...........: 0
Primary port address.....: Not used
Primary port length......: Not used
Secondary port address...: Not used
Secondary port length....: Not used
Interrupt 0..............: 7
Interrupt 1..............: Not used
Slot.....................: 10041
DMA0.....................: Not used
DMA1.....................: Not used
Memory 0 address.........: 0000
Memory 0 length..........: 0400
Memory 1 address.........: Not used
Memory 1 length..........: Not used
[V505-A0-D0:0] HP LOGICAL VOLUME f/w:1.66
Media manager object ID.....: 0x0007
Media manager Object Type...: Device
Device type.................: Magnetic disk
Capacity....................: 858112 MB
Unit Size, in bytes.........: 512
Sectors.....................: 32
Heads.......................: 255
Cylinders...................: 18785
Block size, in bytes........: 4294966784
Activated...................: Yes
Registered..................: Yes
Functional..................: Yes
Writable....................: Yes
Write protected.............: No
Reserved....................: No
Removable...................: No
Read Handicap...............: No
Offline.....................: No
Controller Number...........: 0
Device Number...............: 0
Adapter Number..............: 0
System Type.................: 0x90000
Read after write verify.....: Disabled
DOS Partitioned Media
Media Manager object ID..: 0x0008
Media Manager Object Type: Media
Media type...............: IBM partition
[V505-A0-D0:0-PAA6BA] Free Partition Space
Media Manager object ID......: 0x0019
Media Manager Object Type....: Partition
Activated....................: Yes
Registered...................: Yes
Functional...................: Yes
Reserved.....................: No
Logical partition............: No
Beginning sector of partition: 1429591200
Size, in sectors.............: 328023484
[V505-A0-D0:0-P0] Big DOS; OS/2; Win95 Partition
Media Manager object ID......: 0x0009
Media Manager Object Type....: Partition
Activated....................: Yes
Registered...................: Yes
Functional...................: Yes
Reserved.....................: Yes
Logical partition............: No
Beginning sector of partition: 32
Size, in sectors.............: 4177888
[V505-A0-D0:0-P7F8] NSS Partition
Media Manager object ID......: 0x000A
Media Manager Object Type....: Partition
Activated....................: Yes
Registered...................: Yes
Functional...................: Yes
Reserved.....................: Yes
Logical partition............: Yes
Beginning sector of partition: 4177920
Size, in sectors.............: 32768000
[V505-A0-D0:0-P4678] NSS Partition
Media Manager object ID......: 0x000B
Media Manager Object Type....: Partition
Activated....................: Yes
Registered...................: Yes
Functional...................: Yes
Reserved.....................: Yes
Logical partition............: Yes
Beginning sector of partition: 36945920
Size, in sectors.............: 204800000
[V505-A0-D0:0-P1CD18] NSS Partition
Media Manager object ID......: 0x000C
Media Manager Object Type....: Partition
Activated....................: Yes
Registered...................: Yes
Functional...................: Yes
Reserved.....................: Yes
Logical partition............: Yes
Beginning sector of partition: 241745920
Size, in sectors.............: 40960000
[V505-A0-D0:0-P21B38] NSS Partition
Media Manager object ID......: 0x000D
Media Manager Object Type....: Partition
Activated....................: Yes
Registered...................: Yes
Functional...................: Yes
Reserved.....................: No
Logical partition............: No
Beginning sector of partition: 282705920
Size, in sectors.............: 41943040
[V505-A0-D0:0-P26B38] NSS Partition
Media Manager object ID......: 0x000F
Media Manager Object Type....: Partition
Activated....................: Yes
Registered...................: Yes
Functional...................: Yes
Reserved.....................: No
Logical partition............: No
Beginning sector of partition: 324648960
Size, in sectors.............: 41943040
[V505-A0-D0:0-P2BB38] NSS Partition
Media Manager object ID......: 0x0011
Media Manager Object Type....: Partition
Activated....................: Yes
Registered...................: Yes
Functional...................: Yes
Reserved.....................: No
Logical partition............: No
Beginning sector of partition: 366592000
Size, in sectors.............: 41943040
[V505-A0-D0:0-P30B38] Free Partition Space
Media Manager object ID......: 0x0012
Media Manager Object Type....: Partition
Activated....................: Yes
Registered...................: Yes
Functional...................: Yes
Reserved.....................: No
Logical partition............: No
Beginning sector of partition: 408535040
Size, in sectors.............: 38010880
[V505-A0-D0:0-P353B8] NSS Partition
Media Manager object ID......: 0x0013
Media Manager Object Type....: Partition
Activated....................: Yes
Registered...................: Yes
Functional...................: Yes
Reserved.....................: Yes
Logical partition............: Yes
Beginning sector of partition: 446545920
Size, in sectors.............: 163840000
[V505-A0-D0:0-P48C38] NSS Partition
Media Manager object ID......: 0x0014
Media Manager Object Type....: Partition
Activated....................: Yes
Registered...................: Yes
Functional...................: Yes
Reserved.....................: Yes
Logical partition............: Yes
Beginning sector of partition: 610385920
Size, in sectors.............: 204800000
[V505-A0-D0:0-P612D8] NSS Partition
Media Manager object ID......: 0x0015
Media Manager Object Type....: Partition
Activated....................: Yes
Registered...................: Yes
Functional...................: Yes
Reserved.....................: Yes
Logical partition............: No
Beginning sector of partition: 815185920
Size, in sectors.............: 204800000
[V505-A0-D0:0-P79978] NSS Partition
Media Manager object ID......: 0x0016
Media Manager Object Type....: Partition
Activated....................: Yes
Registered...................: Yes
Functional...................: Yes
Reserved.....................: Yes
Logical partition............: Yes
Beginning sector of partition: 1019985920
Size, in sectors.............: 204800000
[V505-A0-D0:0-P92018] NSS Partition
Media Manager object ID......: 0x0017
Media Manager Object Type....: Partition
Activated....................: Yes
Registered...................: Yes
Functional...................: Yes
Reserved.....................: Yes
Logical partition............: No
Beginning sector of partition: 1224785920
Size, in sectors.............: 204800000
[V505-A0-D0:0-PAA6B8] Free Partition Space
Media Manager object ID......: 0x0018
Media Manager Object Type....: Partition
Activated....................: Yes
Registered...................: Yes
Functional...................: Yes
Reserved.....................: No
Logical partition............: No
Beginning sector of partition: 1429585920
Size, in sectors.............: 5280
End of Storage Device Configuration Information
* Volume Statistics for SYS *
File System................: NSSIDK (Novell Storage Services)
Volume Size................: 15934 MB
Block Size.................: 4 KB
Total Blocks...............: 4079171
Free Blocks................: 3072770
Purgable Blocks............: 158
Not Yet Purgable Blocks....: 0
Total Directory Entries....: 2147483647
Available Directory Entries: 2147439380
Sectors per Block..........: 8
Free Disk Space............: 12003 MB
Purgable Disk Space........: 0 MB
Suballocation..............: OFF
Compression................: OFF
Migration..................: OFF
* Volume Statistics for _ADMIN *
File System................: Unknown
Volume Size................: 4 MB
Block Size.................: 4 KB
Total Blocks...............: 1024
Free Blocks................: 1024
Purgable Blocks............: 0
Not Yet Purgable Blocks....: 0
Total Directory Entries....: 2147483647
Available Directory Entries: 2147483647
Sectors per Block..........: 8
Free Disk Space............: 4 MB
Purgable Disk Space........: 0 MB
Suballocation..............: OFF
Compression................: OFF
Migration..................: OFF
* Volume Statistics for IMAGES *
File System................: NSSIDK (Novell Storage Services)
Volume Size................: 99702 MB
Block Size.................: 4 KB
Total Blocks...............: 25523833
Free Blocks................: 12760577
Purgable Blocks............: 0
Not Yet Purgable Blocks....: 0
Total Directory Entries....: 2147483647
Available Directory Entries: 2147483627
Sectors per Block..........: 8
Free Disk Space............: 49846 MB
Purgable Disk Space........: 0 MB
Suballocation..............: OFF
Compression................: OFF
Migration..................: OFF
* Volume Statistics for PRINTING *
File System................: NSSIDK (Novell Storage Services)
Volume Size................: 19932 MB
Block Size.................: 4 KB
Total Blocks...............: 5102598
Free Blocks................: 4766787
Purgable Blocks............: 55
Not Yet Purgable Blocks....: 0
Total Directory Entries....: 2147483647
Available Directory Entries: 2147480871
Sectors per Block..........: 8
Free Disk Space............: 18620 MB
Purgable Disk Space........: 0 MB
Suballocation..............: OFF
Compression................: OFF
Migration..................: OFF
* Volume Statistics for STAFF *
File System................: NSSIDK (Novell Storage Services)
Volume Size................: 140541 MB
Block Size.................: 4 KB
Total Blocks...............: 35978535
Free Blocks................: 4278115
Purgable Blocks............: 428
Not Yet Purgable Blocks....: 0
Total Directory Entries....: 2147483647
Available Directory Entries: 2147301305
Sectors per Block..........: 8
Free Disk Space............: 16711 MB
Purgable Disk Space........: 1 MB
Suballocation..............: OFF
Compression................: OFF
Migration..................: OFF
* Volume Statistics for FCLTY *
File System................: NSSIDK (Novell Storage Services)
Volume Size................: 120121 MB
Block Size.................: 4 KB
Total Blocks...............: 30751101
Free Blocks................: 6551019
Purgable Blocks............: 2
Not Yet Purgable Blocks....: 0
Total Directory Entries....: 2147483647
Available Directory Entries: 2147231898
Sectors per Block..........: 8
Free Disk Space............: 25589 MB
Purgable Disk Space........: 0 MB
Suballocation..............: OFF
Compression................: OFF
Migration..................: OFF
* Volume Statistics for APPS *
File System................: NSSIDK (Novell Storage Services)
Volume Size................: 79761 MB
Block Size.................: 4 KB
Total Blocks...............: 20418911
Free Blocks................: 8163253
Purgable Blocks............: 0
Not Yet Purgable Blocks....: 0
Total Directory Entries....: 2147483647
Available Directory Entries: 2147246784
Sectors per Block..........: 8
Free Disk Space............: 31887 MB
Purgable Disk Space........: 0 MB
Suballocation..............: OFF
Compression................: OFF
Migration..................: OFF
* Volume Statistics for ACDMC *
File System................: NSSIDK (Novell Storage Services)
Volume Size................: 99700 MB
Block Size.................: 4 KB
Total Blocks...............: 25523381
Free Blocks................: 9816828
Purgable Blocks............: 0
Not Yet Purgable Blocks....: 0
Total Directory Entries....: 2147483647
Available Directory Entries: 2147069762
Sectors per Block..........: 8
Free Disk Space............: 38346 MB
Purgable Disk Space........: 0 MB
Suballocation..............: OFF
Compression................: OFF
Migration..................: OFF
* Volume Statistics for PUPILS *
File System................: NSSIDK (Novell Storage Services)
Volume Size................: 99702 MB
Block Size.................: 4 KB
Total Blocks...............: 25523813
Free Blocks................: 13579469
Purgable Blocks............: 0
Not Yet Purgable Blocks....: 0
Total Directory Entries....: 2147483647
Available Directory Entries: 2147417601
Sectors per Block..........: 8
Free Disk Space............: 53044 MB
Purgable Disk Space........: 0 MB
Suballocation..............: OFF
Compression................: OFF
Migration..................: OFF
Volume Name Name Spaces Loaded
SYS DOS
SYS MACINTOSH
SYS NFS
SYS LONG_NAMES
_ADMIN DOS
_ADMIN MACINTOSH
_ADMIN NFS
_ADMIN LONG_NAMES
IMAGES DOS
IMAGES MACINTOSH
IMAGES NFS
IMAGES LONG_NAMES
PRINTING DOS
PRINTING MACINTOSH
PRINTING NFS
PRINTING LONG_NAMES
STAFF DOS
STAFF MACINTOSH
STAFF NFS
STAFF LONG_NAMES
FCLTY DOS
FCLTY MACINTOSH
FCLTY NFS
FCLTY LONG_NAMES
APPS DOS
APPS MACINTOSH
APPS NFS
APPS LONG_NAMES
ACDMC DOS
ACDMC MACINTOSH
ACDMC NFS
ACDMC LONG_NAMES
PUPILS DOS
PUPILS MACINTOSH
PUPILS NFS
PUPILS LONG_NAMES
************************************************** ***************************Hi.
On 18.01.2012 15:36, gayfield wrote:
>
> Hi Massimo
>
> Many thanks for your quick response. I've been into the console.log and
> pasted the last few entries below :
>
> 17-01-2012 6:19:58 pm: SERVER-5.70-0 [nmID=6001D]
> Cache memory allocator out of available memory.
>
>
> 17-01-2012 6:19:58 pm: SERVER-5.70-0 [nmID=2000A]
> Short term memory allocator is out of memory.
> 1 attempts to get more memory failed.
> request size in bytes 14807040 from Module SWEEP.NLM
>
> Loading Module FSIFIND.NLM [
> OK ]
> Loading Module FSBACK.NLM [
> OK ]
>
> 17-01-2012 8:24:13 pm: SERVER-5.70-0 [nmID=6001D]
> Cache memory allocator out of available memory.
>
>
> 17-01-2012 8:24:13 pm: SERVER-5.70-0 [nmID=2000A]
> Short term memory allocator is out of memory.
> 2 attempts to get more memory failed.
> request size in bytes 11403264 from Module SWEEP.NLM
>
>
> 17-01-2012 8:34:17 pm: SERVER-5.70-0 [nmID=6001D]
> Cache memory allocator out of available memory.
>
>
> 17-01-2012 8:34:17 pm: SERVER-5.70-0 [nmID=2000A]
> Short term memory allocator is out of memory.
> 3 attempts to get more memory failed.
> request size in bytes 15418880 from Module SWEEP.NLM
>
>
> 17-01-2012 8:48:14 pm: SERVER-5.70-0 [nmID=6001D]
> Cache memory allocator out of available memory.
>
>
> 17-01-2012 8:48:14 pm: SERVER-5.70-0 [nmID=2000A]
> Short term memory allocator is out of memory.
> 4 attempts to get more memory failed.
> request size in bytes 14807040 from Module SWEEP.NLM
>
>
> 17-01-2012 8:58:18 pm: SERVER-5.70-0 [nmID=6001D]
> Cache memory allocator out of available memory.
>
>
> 17-01-2012 8:58:18 pm: SERVER-5.70-0 [nmID=2000A]
> Short term memory allocator is out of memory.
> 5 attempts to get more memory failed.
> request size in bytes 14680064 from Module SWEEP.NLM
>
> Hope this better clarifies the situation.
Somewhat. From the time of day, and the loading of commvault modules
inbetween, this looks like a combined backup / AV scan issue. The
requests of Sophos are comparably big in size, and they vary a lot. That
will lead to fragmentation of your memory, until the memory can't be
allocated in one chunk any more. It also *seems* as if Sophos actually
scans the data while it gets backed up. That is *bad*.
CU,
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de -
Error in stored procedure while using dbms_datapump for transportable
Hi,
I'm facing following issue:
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for Solaris: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
====================================================================================
I'm trying to do transportable tablespace through stored procedure with help of DBMS_DATAPUMP, Following is the code :
==================================================================================
create or replace
procedure sp_tts_export(v_tbs_name varchar2) as
idx NUMBER; -- Loop index
JobHandle NUMBER; -- Data Pump job handle
PctComplete NUMBER; -- Percentage of job complete
JobState VARCHAR2(30); -- To keep track of job state
LogEntry ku$_LogEntry; -- For WIP and error messages
JobStatus ku$_JobStatus; -- The job status from get_status
Status ku$_Status; -- The status object returned by get_status
dts varchar2(140):=to_char(sysdate,'YYYYMMDDHH24MISS');
exp_dump_file varchar2(500):=v_tbs_name||'_tts_export_'||dts||'.dmp';
exp_log_file varchar2(500):=v_tbs_name||'_tts_export_'||dts||'.log';
exp_job_name varchar2(500):=v_tbs_name||'_tts_export_'||dts;
dp_dir varchar2(500):='DATA_PUMP_DIR';
log_file UTL_FILE.FILE_TYPE;
log_filename varchar2(500):=exp_job_name||'_main'||'.log';
err_log_file UTL_FILE.FILE_TYPE;
v_db_name varchar2(1000);
v_username varchar2(30);
t_dir_name VARCHAR2(4000);
t_file_name VARCHAR2(4000);
t_sep_pos NUMBER;
t_dir varchar2(30):='temp_0123456789';
v_sqlerrm varchar2(4000);
stmt varchar2(4000);
FUNCTION get_file(filename VARCHAR2, dir VARCHAR2 := 'TEMP')
RETURN VARCHAR2 IS
contents VARCHAR2(32767);
file BFILE := BFILENAME(dir, filename);
BEGIN
DBMS_LOB.FILEOPEN(file, DBMS_LOB.FILE_READONLY);
contents := UTL_RAW.CAST_TO_VARCHAR2(
DBMS_LOB.SUBSTR(file));
DBMS_LOB.CLOSE(file);
RETURN contents;
END;
begin
--execute immediate ('drop tablespace test including contents and datafiles');
--execute immediate ('create tablespace test datafile ''/home/smishr02/test.dbf'' size 10m');
--execute immediate ('create table prestg.test_table (a number) tablespace test');
--execute immediate ('insert into prestg.test_table values (1)');
--commit;
--execute immediate ('alter tablespace test read only');
--dbms_output.put_line('11111111111111111111');
dbms_output.put_line(log_filename||'>>>>>>>>>>>>>>>>>>>>>>>>>>>'|| dp_dir);
log_file:=UTL_FILE.FOPEN (dp_dir, log_filename, 'w');
UTL_FILE.PUT_LINE(log_file,'#####################################################################');
UTL_FILE.PUT_LINE(log_file,'REPORT: GENERATED ON ' || SYSDATE);
UTL_FILE.PUT_LINE(log_file,'#####################################################################');
select global_name,user into v_db_name,v_username from global_name;
UTL_FILE.PUT_LINE(log_file,'Database:'||v_db_name);
UTL_FILE.PUT_LINE(log_file,'user running the job:'||v_username);
UTL_FILE.PUT_LINE(log_file,'for tablespace:'||v_tbs_name);
UTL_FILE.NEW_LINE (log_file);
stmt:='ALTER TABLESPACE '||v_tbs_name || ' read only';
dbms_output.put_line('11111111111111111111'||stmt);
execute immediate (stmt);
UTL_FILE.PUT_LINE(log_file,' '||v_tbs_name || ' altered to read only mode.');
UTL_FILE.NEW_LINE (log_file);
UTL_FILE.PUT_LINE(log_file,'#####################################################################');
UTL_FILE.NEW_LINE (log_file);
UTL_FILE.PUT_LINE(log_file,' Initiating the Datapump engine for TTS export..............');
UTL_FILE.NEW_LINE (log_file);
dbms_output.put_line('11111111111111111111');
JobHandle :=
DBMS_DATAPUMP.OPEN(
operation => 'EXPORT'
*,job_mode => 'TRANSPORTABLE'*
*,remote_link => NULL*
*,job_name => NULL*
--,job_name => exp_job_name
-- ,version => 'LATEST'
UTL_FILE.PUT_LINE(log_file,'Done');
UTL_FILE.NEW_LINE (log_file);
UTL_FILE.PUT_LINE(log_file,' Allocating dumpfile................');
DBMS_DATAPUMP.ADD_FILE(
handle => JobHandle
,filename => exp_dump_file
,directory => dp_dir
,filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_DUMP_FILE
-- ,filesize => '100M'
UTL_FILE.PUT_LINE(log_file,'Done');
UTL_FILE.NEW_LINE (log_file);
UTL_FILE.PUT_LINE(log_file,' Allocating logfile................');
DBMS_DATAPUMP.ADD_FILE(
handle => JobHandle
,filename => exp_log_file
,directory => dp_dir
,filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_LOG_FILE
UTL_FILE.PUT_LINE(log_file,'Done');
UTL_FILE.NEW_LINE (log_file);
UTL_FILE.PUT_LINE(log_file,' Setting attributes................');
DBMS_DATAPUMP.set_parameter(handle => JobHandle,
name=>'TTS_FULL_CHECK',
value=>1);
DBMS_DATAPUMP.METADATA_FILTER(
handle => JobHandle
,NAME => 'TABLESPACE_EXPR'
,VALUE => 'IN ('''||v_tbs_name||''')'
-- ,object_type => 'TABLE'
UTL_FILE.PUT_LINE(log_file,'Done');
UTL_FILE.NEW_LINE (log_file);
UTL_FILE.PUT_LINE(log_file,' Now starting datapump job................');
DBMS_DATAPUMP.START_JOB(JobHandle);
UTL_FILE.PUT_LINE(log_file,'Done');
UTL_FILE.NEW_LINE (log_file);
UTL_FILE.PUT_LINE(log_file,' Monitoring the job................');
--------------Monitor the job
PctComplete := 0;
JobState := 'UNDEFINED';
WHILE(JobState != 'COMPLETED') and (JobState != 'STOPPED')
LOOP
DBMS_DATAPUMP.GET_STATUS(
handle => JobHandle
,mask => 15 -- DBMS_DATAPUMP.ku$_status_job_error + DBMS_DATAPUMP.ku$_status_job_status + DBMS_DATAPUMP.ku$_status_wip
,timeout => NULL
,job_state => JobState
,status => Status
JobStatus := Status.job_status;
-- Whenever the PctComplete value has changed, display it
IF JobStatus.percent_done != PctComplete THEN
DBMS_OUTPUT.PUT_LINE('*** Job percent done = ' || TO_CHAR(JobStatus.percent_done));
PctComplete := JobStatus.percent_done;
END IF;
-- Whenever a work-in progress message or error message arises, display it
IF (BITAND(Status.mask,DBMS_DATAPUMP.ku$_status_wip) != 0) THEN
LogEntry := Status.wip;
ELSE
IF (BITAND(Status.mask,DBMS_DATAPUMP.ku$_status_job_error) != 0) THEN
LogEntry := Status.error;
ELSE
LogEntry := NULL;
END IF;
END IF;
IF LogEntry IS NOT NULL THEN
idx := LogEntry.FIRST;
WHILE idx IS NOT NULL
LOOP
DBMS_OUTPUT.PUT_LINE(LogEntry(idx).LogText);
idx := LogEntry.NEXT(idx);
END LOOP;
END IF;
END LOOP;
--copy the datafiles to data dump dir
UTL_FILE.PUT_LINE(log_file,'Done');
UTL_FILE.NEW_LINE (log_file);
UTL_FILE.PUT_LINE(log_file,' Copying datafiles to dump directory................');
-- grant select on dba_directories to prestg;
declare
cnt number;
begin
select count(*) into cnt from dba_directories
where directory_name=upper(t_dir);
if cnt=1 then
execute immediate('DROP DIRECTORY '||t_dir);
end if;
end;
FOR rec in (select file_name from sys.dba_data_files where tablespace_name=v_tbs_name)
LOOP
t_sep_pos:=instr(rec.file_name,'/',-1);
t_dir_name:=substr(rec.file_name,1,t_sep_pos-1);
t_file_name:=substr(rec.file_name,t_sep_pos+1,length(rec.file_name));
dbms_output.put_line(t_dir_name|| ' ' || t_dir);
dbms_output.put_line(t_file_name);
execute immediate('CREATE DIRECTORY '||t_dir||' AS '''||t_dir_name||'''');
UTL_FILE.PUT_LINE(log_file,' Copying '||rec.file_name||'................');
utl_file.fcopy(t_dir, t_file_name, dp_dir, t_file_name);
UTL_FILE.PUT(log_file,'Done');
execute immediate('DROP DIRECTORY '||t_dir);
END LOOP;
UTL_FILE.NEW_LINE (log_file);
UTL_FILE.PUT_LINE(log_file,' Altering tablespace to read write................');
execute immediate ('ALTER TABLESPACE '||v_tbs_name || ' read write');
UTL_FILE.PUT(log_file,' Done');
err_log_file:=utl_file.fopen(dp_dir, exp_log_file, 'r');
UTL_FILE.NEW_LINE (log_file);
UTL_FILE.PUT_LINE(log_file,' content of export logfile................');
loop
begin
utl_file.get_line(err_log_file,v_sqlerrm);
if v_sqlerrm is null then
exit;
end if;
UTL_FILE.PUT_LINE(log_file,v_sqlerrm);
EXCEPTION
WHEN NO_DATA_FOUND THEN
EXIT;
END;
end loop;
utl_file.fclose(err_log_file);
utl_file.fclose(log_file);
END;
I'm getting following error when DBMS_DATAPUMP.OPEN is called in procedure:
SQL> exec sp_tts_export('TEST');
BEGIN sp_tts_export('TEST'); END;
ERROR at line 1:
ORA-31626: job does not exist
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79
ORA-06512: at "SYS.DBMS_DATAPUMP", line 938
ORA-06512: at "SYS.DBMS_DATAPUMP", line 4566
ORA-06512: at "PRESTG.SP_TTS_EXPORT", line 78
ORA-06512: at line 1
==============================================================================================
This procedure is part of user ABC. I'm getting the above when I'm running this under ABC schema. However I have tested the same procedure under sys schema. When I'm creating same procedure in SYS schema it is running fine. I am clueless on this. Pls help
Thanks
Shailesh
Edited by: shaileshM on Jul 28, 2010 11:15 AMPrivileges acquired via ROLE do NOT apply within named PL/SQL procedures.
Explicit GRANT is required to resolve this issue. -
Error Code 12 When Transport BW Request
Dear All,
I am getting a return code 12 when I execute a BW transport request from DEV to QA. When the transport starts, it actually calls a job , RDDEXECL to run. The job fails with the error :
01.08.2006 14:05:05 Job started
01.08.2006 14:05:05 Step 001 started (program RDDEXECL, variant , user ID DDIC)
01.08.2006 14:05:05 All DB buffers of application server gdcs002q were synchronized
01.08.2006 14:14:57 STDO: Log could not be written on output device T
01.08.2006 14:22:14 Communication Structure /BIC/CS8ZEOPRO02 activated
01.08.2006 14:22:19 Transfer Rule(s) 8ZEOPRO02_AA activated
01.08.2006 14:22:23 Communication Structure /BIC/CS8ZEOPRO02 activated
01.08.2006 14:22:25 ABAP/4 processor: MESSAGE_TYPE_X
01.08.2006 14:22:25 Job cancelled
A ABAP dump was created due to the job failure.
Runtime Error MESSAGE_TYPE_X
Date and Time 01.08.2006 16:56:51
ShrtText
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
Short text of error message:
Serious internal error:
Technical information about the message:
Diagnosis
A serious internal error occurred. It could not be corrected.
Procedure
The following information is available on this error:
1.
2.
3.
4. OSS note
Check the OSS for corresponding notes and create a new problem
message if necessary.
Message classe...... "RSAR"
Number.............. 001
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"MESSAGE_TYPE_X" C
"SAPLRSAC" or "LRSACU75"
"RSAR_TRANSTRUCTURE_ACTIVATE"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "640"
Application server....... "gdcs002q"
Network address.......... "192.168.188.71"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x AMD64 Level"
Character length......... 16 Bits
Pointer length........... 64 Bits
Work process number...... 29
Short dump setting....... "full"
Database server.......... "GDCS002Q"
Database type............ "MSSQL"
Database name............ "BQ1"
Database owner........... "bq1"
Character set............ "C"
SAP kernel............... "640"
Created on............... "May 21 2006 22:47:47"
Created in............... "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version......... "SQL_Server_8.00 "
Patch level.............. "129"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory usage.............
Roll..................... 16192
EM....................... 146644960
Heap..................... 0
Page..................... 2547712
MM Used.................. 82234648
MM Free.................. 51831952
SAP Release.............. "640"
User and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Program............. "SAPLRSAC"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "SAPLRSAC" in
"RSAR_TRANSTRUCTURE_ACTIVATE".
The main program was "RDDEXECU ".
The termination occurred in line 536 of the source code of the (Include)
program "LRSACU75"
of the source code of program "LRSACU75" (when calling the editor 5360).
The program "SAPLRSAC" was started as a background job.
Job name........ "RDDEXECL"
Job initiator... "DDIC"
Job number...... 16421301
Source Code Extract
Line
SourceCde
506
IF g_subrc NE 0.
507
MESSAGE x001.
508
ENDIF.
509
Check new version neccessary
510
l_curr_version = c_s_is_admin-odsversion.
511
512
IF l_new_version EQ rs_c_true.
513
IF i_without_versioning EQ rs_c_true.
514
MESSAGE e023 WITH c_s_is_admin-odsname_tech
515
c_s_is_admin-isource
516
RAISING no_psa_version_allowed.
517
ELSEIF i_without_versioning EQ 'C' AND
518
i_without_transport EQ rs_c_true.
519
*-- special handling for migration.
520
*- current system is target system no transport request
521
*- necessary if a new version is needed
522
ELSEIF i_without_versioning EQ 'C' AND
523
i_without_transport EQ rs_c_false.
524
RAISE inconsistency.
525
ENDIF. .
526
527
IF i_objtype = rsa_c_istype-data.
528
check type of InfoSource first
529
SELECT SINGLE issrctype FROM rsis
530
INTO l_isrctype
531
WHERE isource = c_s_is_admin-isource
532
AND objvers = rs_c_objvers-active.
533
IF sy-subrc <> 0 OR l_isrctype = rsarc_c_issrctype-ods.
534
if generated ODS InfoSource,
535
no PSA versioning possible
>>>>>
MESSAGE x001.
537
ENDIF.
538
ENDIF.
539
l_next_version = l_curr_version + 1.
540
c_s_is_admin-odsversion = l_next_version.
541
l_transtru_odsname+13(3) = l_next_version.
542
Don't use old progname but create new one
543
CLEAR l_progname_ods.
544
ELSE.
545
l_next_version = l_curr_version.
546
ENDIF.
547
548
ENDIF.
549
set transtru_names for IDoc
550
c_s_is_admin-odsname = i_transtru_name.
551
c_s_is_admin-odsname_tech = l_transtru_odsname.
552
WHEN OTHERS.
553
ENDCASE.
554
555
save Transfer rules as active version
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
1
SY-TABIX
0
SY-DBCNT
1
SY-FDPOS
10
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Execute Post-Import Methods and XPRAs for Transport Request
SY-MSGTY
X
SY-MSGID
RSAR
SY-MSGNO
001
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No. Ty. Program Include Line
Name
13 FUNCTION SAPLRSAC LRSACU75 536
RSAR_TRANSTRUCTURE_ACTIVATE
12 FORM SAPLRSAC_TRANSPORT LRSAC_TRANSPORTF02 1709
ACTIVATE_ISTS
11 FUNCTION SAPLRSAC_TRANSPORT LRSAC_TRANSPORTU68 124
RSAR_CODS_INFOSOURCE_ACTIVATE
10 FUNCTION SAPLRSAC_TRANSPORT LRSAC_TRANSPORTU67 134
RSAR_EXPORT_METADATA_GEN
9 METHOD CL_RSD_ODSO===================CP CL_RSD_ODSO===================CM00M 52
CL_RSD_ODSO=>IF_RSO_TLOGO_MAINTAIN_INT~AFTER_ACTIVATION
8 METHOD CL_RSO_TLOGO_COLLECTION=======CP CL_RSO_TLOGO_COLLECTION=======CM010 333
CL_RSO_TLOGO_COLLECTION=>ACTIVATE_ONE_STEP
7 METHOD CL_RSO_TLOGO_COLLECTION=======CP CL_RSO_TLOGO_COLLECTION=======CM009 216
CL_RSO_TLOGO_COLLECTION=>ACTIVATE_INTERNAL
6 METHOD CL_RSO_TLOGO_COLLECTION=======CP CL_RSO_TLOGO_COLLECTION=======CM004 6
CL_RSO_TLOGO_COLLECTION=>ACTIVATE
5 FUNCTION SAPLRSDG_ODSO LRSDG_ODSOU02 98
RS_ODSO_AFTER_IMPORT
4 FUNCTION SAPLRSVERS LRSVERSU03 127
RS_AFTER_IMPORT
3 FORM SAPLSCTS_EXE_EXP LSCTS_EXE_EXPF02 138
CALL_IMP_METHODS
2 FUNCTION SAPLSCTS_EXE_EXP LSCTS_EXE_EXPU02 94
TRINT_CALL_AFTER_IMP_METHOD
1 EVENT RDDEXECU RDDEXECU 186
START-OF-SELECTION
Chosen variables
Name
Val.
No. 13 Ty. FUNCTION
Name RSAR_TRANSTRUCTURE_ACTIVATE
I_DM_SEVERITY
2
0
0
0
I_LOGSYS
BQ1CLNT200
4534445333
2113CE4200
0000000000
0000000000
I_NO_PROG_GENERATE
2
0
0
0
I_OBJECT
8ZEOPRO02
354455433222222222222222222222
8A5F02F02000000000000000000000
000000000000000000000000000000
000000000000000000000000000000
I_OBJTYPE
D
4
4
0
0
I_SEGMENT_ID
2
0
0
0
I_TRANSTRU_NAME
8ZEOPRO02_AA
354455433544222222222222222
8A5F02F02F11000000000000000
000000000000000000000000000
000000000000000000000000000
I_T_TSFIELD
Table IT_1551158[17x632]
FUNCTION=RSAR_TRANSTRUCTURE_ACTIVATEDATA=I_T_TSFIELD
Table reference: 4904
TABH+ 0(20) = 88666064FE070000000000000000000000000000
TABH+ 20(20) = 2813000036AB17001100000078020000FFFFFFFF
TABH+ 40(16) = 046E01000038000010000000C9248400
store = 0x88666064FE070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 4904 (0x28130000)
label = 1551158 (0x36AB1700)
fill = 17 (0x11000000)
leng = 632 (0x78020000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000285
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 1 (ItIndexLinear)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x1857B168FE070000
pghook = 0x80E67064FE070000
idxPtr = 0x70C90864FE070000
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 32 (0x20000000)
lineAlloc = 32 (0x20000000)
store_id = 957569 (0x819C0E00)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
I_T_TSMAPPING
Table IT_1551159[17x2372]
FUNCTION=RSAR_TRANSTRUCTURE_ACTIVATEDATA=I_T_TSMAPPING
Table reference: 4956
TABH+ 0(20) = B0932263FE070000000000000000000000000000
TABH+ 20(20) = 5C13000037AB17001100000044090000FFFFFFFF
TABH+ 40(16) = 046E01008036000004000000C9248400
store = 0xB0932263FE070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 4956 (0x5C130000)
label = 1551159 (0x37AB1700)
fill = 17 (0x11000000)
leng = 2372 (0x44090000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000277
occu = 4 (0x04000000)
access = 1 (ItAccessStandard)
idxKind = 1 (ItIndexLinear)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x70FB0564FE070000
pghook = 0xE0E77064FE070000
idxPtr = 0x60EB1E64FE070000
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 32 (0x20000000)
lineAlloc = 20 (0x14000000)
store_id = 957570 (0x829C0E00)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
I_USE_PROPOSAL
X
5
8
0
0
I_WITHOUT_LOG
X
5
8
0
0
I_WITHOUT_TRANSPORT
X
5
8
0
0
I_WITHOUT_VERSIONING
2
0
0
0
C_S_IS_ADMIN
8ZEOPRO02_AA M T 8ZEOPRO02_AA 000/BIC/CAAA8ZEOPRO02
3544554335442222222222222224222252354455433544222222222222222222333244424444354455433222222222
8A5F02F02F11000000000000000D0000408A5F02F02F11000000000000000000000F293F31118A5F02F02000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_S_IS_ADMIN-ISOURCE
8ZEOPRO02
354455433222222222222222222222
8A5F02F02000000000000000000000
000000000000000000000000000000
000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
G_S_RSIS-COMSTRU
8ZEOPRO02
354455433222222222222222222222
8A5F02F02000000000000000000000
000000000000000000000000000000
000000000000000000000000000000
RS_C_OBJVERS-ACTIVE
A
4
1
0
0
L_ISRCTYPE
O
4
F
0
0
SY-SUBRC
0
0000
0000
SYST-REPID
SAPLRSAC
5454554422222222222222222222222222222222
310C231300000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
RSARC_C_ISSRCTYPE-ODS
O
4
F
0
0
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-REPID
SAPLRSAC
5454554422222222222222222222222222222222
310C231300000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-MSGID
RSAR
55452222222222222222
23120000000000000000
00000000000000000000
00000000000000000000
MAXCHARLEN
000255
333333
000255
000000
000000
SPACE
2
0
0
0
SY-MSGNO
001
333
001
000
000
RS_C_OBJ_TABL
TABL
5444
412C
0000
0000
SY-MSGV1
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_CURR_VERSION
000
333
000
000
000
L_NEXT_VERSION
000
333
000
000
000
DB6_MIN
003800
333333
003800
000000
000000
L_PROGNAME_ODS
GP9HAHZJDTVMUODQUVHPSYC02JZ
4534445445545445554555433452222222222222
709818AA446D5F41568039302AA0000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
No. 12 Ty. FORM
Name ACTIVATE_ISTS
L_NO_PROG_GENERATE
2
0
0
0
L_T_TR_PROT
Table[initial]
E_SUBRC
0
0000
0000
SYST-REPID
SAPLRSAC_TRANSPORT
5454554455544554552222222222222222222222
310C2313F421E30F240000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
L_S_ISOSMAP-LOGSYS
BQ1CLNT200
4534445333
2113CE4200
0000000000
0000000000
L_S_ISOSMAP-OLTPSOURCE
8ZEOPRO02
354455433222222222222222222222
8A5F02F02000000000000000000000
000000000000000000000000000000
000000000000000000000000000000
L_S_ISOSMAP-ISTYPE
D
4
4
0
0
P_SEGID
2
0
0
0
L_TRANSTRU_NEW
8ZEOPRO02_AA
354455433544222222222222222
8A5F02F02F11000000000000000
000000000000000000000000000
000000000000000000000000000
L_T_TSFIELDSEL
Table IT_1551115[17x632]
FUNCTION-POOL=RSAC_TRANSPORTFORM=ACTIVATE_ISTSDATA=L_T_TSFIELDSEL
Table reference: 4207
TABH+ 0(20) = 88666064FE070000000000000000000000000000
TABH+ 20(20) = 6F1000000BAB17001100000078020000FFFFFFFF
TABH+ 40(16) = 046E01000038000010000000C9248400
store = 0x88666064FE070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 4207 (0x6F100000)
label = 1551115 (0x0BAB1700)
fill = 17 (0x11000000)
leng = 632 (0x78020000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000285
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 1 (ItIndexLinear)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x1857B168FE070000
pghook = 0x80E67064FE070000
idxPtr = 0x70C90864FE070000
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 32 (0x20000000)
lineAlloc = 32 (0x20000000)
store_id = 957569 (0x819C0E00)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
L_T_TSMAPPING
Table IT_1551116[17x2372]
FUNCTION-POOL=RSAC_TRANSPORTFORM=ACTIVATE_ISTSDATA=L_T_TSMAPPING
Table reference: 3062
TABH+ 0(20) = B0932263FE070000000000000000000000000000
TABH+ 20(20) = F60B00000CAB17001100000044090000FFFFFFFF
TABH+ 40(16) = 046E01008036000004000000C9248400
store = 0xB0932263FE070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 3062 (0xF60B0000)
label = 1551116 (0x0CAB1700)
fill = 17 (0x11000000)
leng = 2372 (0x44090000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000277
occu = 4 (0x04000000)
access = 1 (ItAccessStandard)
idxKind = 1 (ItIndexLinear)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x70FB0564FE070000
pghook = 0xE0E77064FE070000
idxPtr = 0x60EB1E64FE070000
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 32 (0x20000000)
lineAlloc = 20 (0x14000000)
store_id = 957570 (0x829C0E00)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
P_SUGGEST_AND_SAVE
X
5
8
0
0
RS_C_TRUE
X
5
8
0
0
L_WITHOUT_TRANSPORT
X
5
8
0
0
L_S_ADMIN
8ZEOPRO02_AA M T 8ZEOPRO02_AA 000/BIC/CAAA8ZEOPRO02
3544554335442222222222222224222252354455433544222222222222222222333244424444354455433222222222
8A5F02F02F11000000000000000D0000408A5F02F02F11000000000000000000000F293F31118A5F02F02000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
SY-REPID
SAPLRSAC_TRANSPORT
5454554455544554552222222222222222222222
310C2313F421E30F240000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_SPACE
2
0
0
0
No. 11 Ty. FUNCTION
Name RSAR_CODS_INFOSOURCE_ACTIVATE
I_DATCLS
22222
00000
00000
00000
I_SIZCAT
22
00
00
00
I_T_OSFIELDMAP
Table IT_1547853[17x204]
FUNCTION=RSAR_EXPORT_METADATA_GENDATA=L_T_OSFIELDMAP
Table reference: 3042
TABH+ 0(20) = 88FF0A64FE070000A8FC4164FE07000000000000
TABH+ 20(20) = E20B00004D9E170011000000CC000000FFFFFFFF
TABH+ 40(16) = 04900300603B000010000000C1248400
store = 0x88FF0A64FE070000
ext1 = 0xA8FC4164FE070000
shmId = 0 (0x00000000)
id = 3042 (0xE20B0000)
label = 1547853 (0x4D9E1700)
fill = 17 (0x11000000)
leng = 204 (0xCC000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000303
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x007EF563FE070000
pghook = 0xA0BD2565FE070000
idxPtr = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 48 (0x30000000)
lineAlloc = 48 (0x30000000)
store_id = 956282 (0x7A970E00)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
hsdir = 0x0000000000000000
ext2 = 0xC8FFF263FE070000
>>>>> 2nd level extension part <<<<<
tabhBack = 0x904C8864FE070000
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
E_T_MESSAGES
Table IT_1549098[6x1376]
FUNCTION=RSAR_EXPORT_METADATA_GENDATA=L_T_MESSAGES
Table reference: 4318
TABH+ 0(20) = 705E1064FE070000000000000000000000000000
TABH+ 20(20) = DE1000002AA317000600000060050000FFFFFFFF
TABH+ 40(16) = 04AD0000D010000008000000C1308000
store = 0x705E1064FE070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 4318 (0xDE100000)
label = 1549098 (0x2AA31700)
fill = 6 (0x06000000)
leng = 1376 (0x60050000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000076
occu = 8 (0x08000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x88731964FE070000
pghook = 0x0000000000000000
idxPtr = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 8 (0x08000000)
lineAlloc = 8 (0x08000000)
store_id = 956709 (0x25990E00)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
E_T_TLOGOHi Mike,
We have had this problem. Please delete the change log table of the ODS in the QA or Prod system (whichever is the target for your transport request) and then reimport the transport request.
<i>
534
if generated ODS InfoSource,
| 535|* no PSA versioning possible |</i>
Hope this helps... -
Stock transport order between storage locations and assignment category type E not in MRP
Hello Gurus,
I have a stock transport order between 2 storage location which belongs to the same plant. Besides the stock transport order is allocated to a sales order (account assigment category E). When I run the MD03, the system take into account the quantity of the stock transport order as a future entry and this is wrong. I need that the MRP has not into account the stock transport order as an entry.
As an important information, If I modify the stock transport order removing the account asignment category E (sales order), then the MRP doesn't take into account it, so this is correct.
Could anybody tell me how to get it?
Thanks in advanced.Laura,
It is normal that MRP will consider an STO as a receipt element; this is basic planning. It is unclear to me why you think you do not want it to do so, but I will assume you have some logical reason.
Contrary to what some others may have suggested, changing the scope of check for availability checking has no effect on which elements are considered for MRP. MRP is a completely separate functionality from Availability Check.
For Location > Location STOs (within a plant), then, you normally have the receipt element of the STO in the destination storage location, and the requirements element of an equal amount in the source storage location. Net of these two elements is zero, unless you have already issued the STO at the source location.
Changing the Account assignment from "E" means that the STO will not be relevant for your Sales order (in other words, when you receive this STO into the destination storage location, it cannot be used for your sales order). In a general MTO scenario, it also means that the proceeds of this STO (the stock you received) cannot be used for ANY sales orders.
One way that some people make an STO 'not relevant' for MRP is to alter the destination storage location such that it is not relevant for MRP. You can change the MRP relevancy of the storage location in MM02 > MRP4 tab
Best Regards,
DB49 -
ICMP Timeout Alarm due to TCP Protocol Memory Allocation Failure ?
Hello Experts ,
>> Device uptime suggests there was no reboot
ABCSwitch uptime is 28 weeks, 13 hours, 50 minutes
System returned to ROM by power-on
System restarted at 13:09:45 UTC Mon Aug 5 2013
System image file is "flash:c2950-i6k2l2q4-mz.121-22.EA12.bin"
>> But observed logs mentioning Memory Allocation Failure for TCP Protocol Process ( Process ID 43) due to Memory Fragmentation
003943: Feb 18 02:14:27.393 UTC: %SYS-2-MALLOCFAIL: Memory allocation of 36000 bytes failed from 0x801E876C, alignment 0
Pool: Processor Free: 120384 Cause: Memory fragmentation
Alternate Pool: I/O Free: 682800 Cause: Memory fragmentation
-Process= "TCP Protocols", ipl= 0, pid= 43
-Traceback= 801C422C 801C9ED0 801C5264 801E8774 801E4CDC 801D9A8C 8022E324 8022E4BC
003944: Feb 18 02:14:27.397 UTC: %SYS-2-CFORKMEM: Process creation of TCP Command failed (no memory).
-Process= "TCP Protocols", ipl= 0, pid= 43
-Traceback= 801E4D54 801D9A8C 8022E324 8022E4BC
According to Cisco documentation for Troubleshooting Memory issues on Cisco IOS 12.1 (http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-software-releases-121-mainline/6507-mallocfail.html#tshoot4 ), which suggests the TCP Protocols Process could not be started due to Memory being fragmented
Memory Fragmentation Problem or Bug
This situation means that a process has consumed a large amount of processor memory and then released most or all of it, leaving fragments of memory still allocated either by this process, or by other processes that allocated memory during the problem. If the same event occurs several times, the memory may fragment into very small blocks, to the point where all processes requiring a larger block of memory cannot get the amount of memory that they need. This may affect router operation to the extent that you cannot connect to the router and get a prompt if the memory is badly fragmented.
This problem is characterized by a low value in the "Largest" column (under 20,000 bytes) of the show memory command, but a sufficient value in the "Freed" column (1MB or more), or some other wide disparity between the two columns. This may happen when the router gets very low on memory, since there is no defragmentation routine in the IOS.
If you suspect memory fragmentation, shut down some interfaces. This may free the fragmented blocks. If this works, the memory is behaving normally, and all you have to do is add more memory. If shutting down interfaces doesn't help, it may be a bug. The best course of action is to contact your Cisco support representative with the information you have collected.
>>Further TCP -3- FORKFAIL logs were seen
003945: Feb 18 02:14:27.401 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
003946: Feb 18 02:14:27.585 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
003947: Feb 18 02:14:27.761 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
003948: Feb 18 02:14:27.929 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
003949: Feb 18 02:14:29.149 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
According to Error Explanation from Cisco Documentation (http://www.cisco.com/c/en/us/td/docs/ios/12_2sx/system/messages/122sxsms/sm2sx09.html#wp1022051)
suggests the TCP handles from a client could not be created or initialized
Error Message %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
Explanation The system failed to create a process to handle requests from a client. This condition could be caused by insufficient memory.
Recommended Action Reduce other system activity to ease memory demands.
But I am still not sure about the exact root cause is as
1.The GET/GETNEXT / GET BULK messages from SNMP Manager (Here, IBM Tivoli Netcool ) uses default SNMP Port 161 which is
UDP and not TCP
2. If its ICMP Polling failure from IBM Tivoli Netcool , ICMP is Protocol Number 1 in Internet Layer of TCP/IP Protocol Suite and TCP is Protocol Number 6 in the Transport Layer of TCP/IP Protocol Suite .
So I am still not sure how TCP Protocol Process Failure could have caused ICMP Timeout . Please help !
Could you please help me on what TCP Protocol Process handles in a Cisco Switch ?
Regards,
AnupHello Experts ,
>> Device uptime suggests there was no reboot
ABCSwitch uptime is 28 weeks, 13 hours, 50 minutes
System returned to ROM by power-on
System restarted at 13:09:45 UTC Mon Aug 5 2013
System image file is "flash:c2950-i6k2l2q4-mz.121-22.EA12.bin"
>> But observed logs mentioning Memory Allocation Failure for TCP Protocol Process ( Process ID 43) due to Memory Fragmentation
003943: Feb 18 02:14:27.393 UTC: %SYS-2-MALLOCFAIL: Memory allocation of 36000 bytes failed from 0x801E876C, alignment 0
Pool: Processor Free: 120384 Cause: Memory fragmentation
Alternate Pool: I/O Free: 682800 Cause: Memory fragmentation
-Process= "TCP Protocols", ipl= 0, pid= 43
-Traceback= 801C422C 801C9ED0 801C5264 801E8774 801E4CDC 801D9A8C 8022E324 8022E4BC
003944: Feb 18 02:14:27.397 UTC: %SYS-2-CFORKMEM: Process creation of TCP Command failed (no memory).
-Process= "TCP Protocols", ipl= 0, pid= 43
-Traceback= 801E4D54 801D9A8C 8022E324 8022E4BC
According to Cisco documentation for Troubleshooting Memory issues on Cisco IOS 12.1 (http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-software-releases-121-mainline/6507-mallocfail.html#tshoot4 ), which suggests the TCP Protocols Process could not be started due to Memory being fragmented
Memory Fragmentation Problem or Bug
This situation means that a process has consumed a large amount of processor memory and then released most or all of it, leaving fragments of memory still allocated either by this process, or by other processes that allocated memory during the problem. If the same event occurs several times, the memory may fragment into very small blocks, to the point where all processes requiring a larger block of memory cannot get the amount of memory that they need. This may affect router operation to the extent that you cannot connect to the router and get a prompt if the memory is badly fragmented.
This problem is characterized by a low value in the "Largest" column (under 20,000 bytes) of the show memory command, but a sufficient value in the "Freed" column (1MB or more), or some other wide disparity between the two columns. This may happen when the router gets very low on memory, since there is no defragmentation routine in the IOS.
If you suspect memory fragmentation, shut down some interfaces. This may free the fragmented blocks. If this works, the memory is behaving normally, and all you have to do is add more memory. If shutting down interfaces doesn't help, it may be a bug. The best course of action is to contact your Cisco support representative with the information you have collected.
>>Further TCP -3- FORKFAIL logs were seen
003945: Feb 18 02:14:27.401 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
003946: Feb 18 02:14:27.585 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
003947: Feb 18 02:14:27.761 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
003948: Feb 18 02:14:27.929 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
003949: Feb 18 02:14:29.149 UTC: %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
-Traceback= 8022E33C 8022E4BC
According to Error Explanation from Cisco Documentation (http://www.cisco.com/c/en/us/td/docs/ios/12_2sx/system/messages/122sxsms/sm2sx09.html#wp1022051)
suggests the TCP handles from a client could not be created or initialized
Error Message %TCP-3-FORKFAIL: Failed to start a process to negotiate options.
Explanation The system failed to create a process to handle requests from a client. This condition could be caused by insufficient memory.
Recommended Action Reduce other system activity to ease memory demands.
But I am still not sure about the exact root cause is as
1.The GET/GETNEXT / GET BULK messages from SNMP Manager (Here, IBM Tivoli Netcool ) uses default SNMP Port 161 which is
UDP and not TCP
2. If its ICMP Polling failure from IBM Tivoli Netcool , ICMP is Protocol Number 1 in Internet Layer of TCP/IP Protocol Suite and TCP is Protocol Number 6 in the Transport Layer of TCP/IP Protocol Suite .
So I am still not sure how TCP Protocol Process Failure could have caused ICMP Timeout . Please help !
Could you please help me on what TCP Protocol Process handles in a Cisco Switch ?
Regards,
Anup -
RID Master not allocating new rid pool
Hi guys,
I am having some problems with my server. I am unable to create new AD objects with the message, the directory has exhausted the pool of relative identifiers. I have a SBS 2003 environment with only that as the DC. However, a while ago, the previous
admin promoted another server (Server 2003) as a Backup DC and later on the network was split and the Secondary DC no longer connected to the domain. It was not demoted or anything like that. The network was split in two and now after almost a year I am unable
to create new objects. The PDC has all the FSMO roles as indicated when i run the netdom query fsmo command. Below is the dcdiag /v output:
Domain Controller Diagnosis
Performing initial setup:
* Verifying that the local machine wsgpdc, is a DC.
* Connecting to directory service on server wsgpdc.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\WSGPDC
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... WSGPDC passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\WSGPDC
Starting test: Replications
* Replications Check
[Replications Check,WSGPDC] Inbound replication is disabled.
To correct, run "repadmin /options WSGPDC -DISABLE_INBOUND_REPL"
[Replications Check,WSGPDC] Outbound replication is disabled.
To correct, run "repadmin /options WSGPDC -DISABLE_OUTBOUND_REPL"
......................... WSGPDC failed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC WSGPDC.
* Security Permissions Check for
DC=ForestDnsZones,DC=WSG,DC=local
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=WSG,DC=local
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=WSG,DC=local
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=WSG,DC=local
(Configuration,Version 2)
* Security Permissions Check for
DC=WSG,DC=local
(Domain,Version 2)
......................... WSGPDC passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\WSGPDC\netlogon
Verified share \\WSGPDC\sysvol
......................... WSGPDC passed test NetLogons
Starting test: Advertising
The DC WSGPDC is advertising itself as a DC and having a DS.
The DC WSGPDC is advertising as an LDAP server
The DC WSGPDC is advertising as having a writeable directory
The DC WSGPDC is advertising as a Key Distribution Center
The DC WSGPDC is advertising as a time server
The DS WSGPDC is advertising as a GC.
......................... WSGPDC passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=WSGPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WSG,DC=local
Role Domain Owner = CN=NTDS Settings,CN=WSGPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WSG,DC=local
Role PDC Owner = CN=NTDS Settings,CN=WSGPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WSG,DC=local
Role Rid Owner = CN=NTDS Settings,CN=WSGPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WSG,DC=local
Role Infrastructure Update Owner = CN=NTDS Settings,CN=WSGPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WSG,DC=local
......................... WSGPDC passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 2609 to 1073741823
* wsgpdc.WSG.local is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 2109 to 2608
* rIDPreviousAllocationPool is 2109 to 2608
* rIDNextRID: 2608
* Warning :Next rid pool not allocated
* Warning :There is less than 0% available RIDs in the current pool
......................... WSGPDC passed test RidManager
Starting test: MachineAccount
Checking machine account for DC WSGPDC on DC WSGPDC.
* SPN found :LDAP/wsgpdc.WSG.local/WSG.local
* SPN found :LDAP/wsgpdc.WSG.local
* SPN found :LDAP/WSGPDC
* SPN found :LDAP/wsgpdc.WSG.local/WSG
* SPN found :LDAP/2af33017-abf3-4f05-9b9c-c19eb3868401._msdcs.WSG.local
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/2af33017-abf3-4f05-9b9c-c19eb3868401/WSG.local
* SPN found :HOST/wsgpdc.WSG.local/WSG.local
* SPN found :HOST/wsgpdc.WSG.local
* SPN found :HOST/WSGPDC
* SPN found :HOST/wsgpdc.WSG.local/WSG
* SPN found :GC/wsgpdc.WSG.local/WSG.local
......................... WSGPDC passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
IsmServ Service is stopped on [WSGPDC]
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... WSGPDC failed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
WSGPDC is in domain DC=WSG,DC=local
Checking for CN=WSGPDC,OU=Domain Controllers,DC=WSG,DC=local in domain DC=WSG,DC=local on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=WSGPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WSG,DC=local in domain CN=Configuration,DC=WSG,DC=local on 1 servers
Object is up-to-date on all servers.
......................... WSGPDC passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... WSGPDC passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
An Error Event occured. EventID: 0xC0003500
Time Generated: 04/29/2014 06:19:58
(Event String could not be retrieved)
......................... WSGPDC failed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15 minutes.
......................... WSGPDC passed test kccevent
Starting test: systemlog
* The System Event log test
An Error Event occured. EventID: 0x00000457
Time Generated: 04/29/2014 18:58:21
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/29/2014 18:58:22
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/29/2014 18:58:22
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/29/2014 18:58:22
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/29/2014 18:58:23
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/29/2014 18:58:23
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/29/2014 18:58:24
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/29/2014 18:58:31
(Event String could not be retrieved)
......................... WSGPDC failed test systemlog
Test omitted by user request: VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)
CN=WSGPDC,OU=Domain Controllers,DC=WSG,DC=local and backlink on
CN=WSGPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WSG,DC=local
are correct.
The system object reference (frsComputerReferenceBL)
CN=WSGPDC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=WSG,DC=local
and backlink on CN=WSGPDC,OU=Domain Controllers,DC=WSG,DC=local are
correct.
The system object reference (serverReferenceBL)
CN=WSGPDC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=WSG,DC=local
and backlink on
CN=NTDS Settings,CN=WSGPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WSG,DC=local
are correct.
......................... WSGPDC passed test VerifyReferences
Test omitted by user request: VerifyEnterpriseReferences
Test omitted by user request: CheckSecurityError
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : WSG
Starting test: CrossRefValidation
......................... WSG passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... WSG passed test CheckSDRefDom
Running enterprise tests on : WSG.local
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... WSG.local passed test Intersite
Starting test: FsmoCheck
GC Name: \\wsgpdc.WSG.local
Locator Flags: 0xe00001fd
PDC Name: \\wsgpdc.WSG.local
Locator Flags: 0xe00001fd
Time Server Name: \\wsgpdc.WSG.local
Locator Flags: 0xe00001fd
Preferred Time Server Name: \\wsgpdc.WSG.local
Locator Flags: 0xe00001fd
KDC Name: \\wsgpdc.WSG.local
Locator Flags: 0xe00001fd
......................... WSG.local passed test FsmoCheck
Test omitted by user request: DNS
Test omitted by user request: DNS
Also, another problem I am experiencing seems to point to my DNS service which also runs on the same machine. When I try to open Active Directory snap ins, it indicates that the domain does not exist or cannot be contacted and the AD is unable to load.
I'd really appreciate any help at the moment. Thanks in advance.
ShawnIdan,
Yes I followed the article regarding removing data in AD with NTDSUTIL. There is one domain and one site, but it states that there is "no current server" and "no current naming context"
My TCP/IP config was set to 127.0.0.1 but then I changed it to point to its static IP Address, but I stumbled onto a best practice article which indicated that the 127 address was preferred, so I changed it back. I changed it as you said and ran the commands
you asked for:
Domain Controller Diagnosis
Performing initial setup:
* Verifying that the local machine wsgpdc, is a DC.
* Connecting to directory service on server wsgpdc.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\WSGPDC
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... WSGPDC passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\WSGPDC
Starting test: Replications
* Replications Check
[Replications Check,WSGPDC] Inbound replication is disabled.
To correct, run "repadmin /options WSGPDC -DISABLE_INBOUND_REPL"
[Replications Check,WSGPDC] Outbound replication is disabled.
To correct, run "repadmin /options WSGPDC -DISABLE_OUTBOUND_REPL"
......................... WSGPDC failed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC WSGPDC.
* Security Permissions Check for
DC=ForestDnsZones,DC=WSG,DC=local
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=WSG,DC=local
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=WSG,DC=local
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=WSG,DC=local
(Configuration,Version 2)
* Security Permissions Check for
DC=WSG,DC=local
(Domain,Version 2)
......................... WSGPDC passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\WSGPDC\netlogon
Verified share \\WSGPDC\sysvol
......................... WSGPDC passed test NetLogons
Starting test: Advertising
The DC WSGPDC is advertising itself as a DC and having a DS.
The DC WSGPDC is advertising as an LDAP server
The DC WSGPDC is advertising as having a writeable directory
The DC WSGPDC is advertising as a Key Distribution Center
The DC WSGPDC is advertising as a time server
The DS WSGPDC is advertising as a GC.
......................... WSGPDC passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=WSGPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WSG,DC=local
Role Domain Owner = CN=NTDS Settings,CN=WSGPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WSG,DC=local
Role PDC Owner = CN=NTDS Settings,CN=WSGPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WSG,DC=local
Role Rid Owner = CN=NTDS Settings,CN=WSGPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WSG,DC=local
Role Infrastructure Update Owner = CN=NTDS Settings,CN=WSGPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WSG,DC=local
......................... WSGPDC passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 2609 to 1073741823
* wsgpdc.WSG.local is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 2109 to 2608
* rIDPreviousAllocationPool is 2109 to 2608
* rIDNextRID: 2608
* Warning :Next rid pool not allocated
* Warning :There is less than 0% available RIDs in the current pool
......................... WSGPDC passed test RidManager
Starting test: MachineAccount
Checking machine account for DC WSGPDC on DC WSGPDC.
* SPN found :LDAP/wsgpdc.WSG.local/WSG.local
* SPN found :LDAP/wsgpdc.WSG.local
* SPN found :LDAP/WSGPDC
* SPN found :LDAP/wsgpdc.WSG.local/WSG
* SPN found :LDAP/2af33017-abf3-4f05-9b9c-c19eb3868401._msdcs.WSG.local
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/2af33017-abf3-4f05-9b9c-c19eb3868401/WSG.local
* SPN found :HOST/wsgpdc.WSG.local/WSG.local
* SPN found :HOST/wsgpdc.WSG.local
* SPN found :HOST/WSGPDC
* SPN found :HOST/wsgpdc.WSG.local/WSG
* SPN found :GC/wsgpdc.WSG.local/WSG.local
......................... WSGPDC passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
IsmServ Service is stopped on [WSGPDC]
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... WSGPDC failed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
WSGPDC is in domain DC=WSG,DC=local
Checking for CN=WSGPDC,OU=Domain Controllers,DC=WSG,DC=local in domain DC=WSG,DC=local on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=WSGPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WSG,DC=local in domain CN=Configuration,DC=WSG,DC=local on 1 servers
Object is up-to-date on all servers.
......................... WSGPDC passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... WSGPDC passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
An Error Event occured. EventID: 0xC0003500
Time Generated: 04/30/2014 06:17:45
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x800034FA
Time Generated: 04/30/2014 06:17:45
(Event String could not be retrieved)
......................... WSGPDC failed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15 minutes.
......................... WSGPDC passed test kccevent
Starting test: systemlog
* The System Event log test
An Error Event occured. EventID: 0x00000457
Time Generated: 04/30/2014 15:45:49
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/30/2014 15:45:49
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/30/2014 15:45:50
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/30/2014 15:45:50
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/30/2014 15:45:51
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/30/2014 15:45:51
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/30/2014 15:45:58
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/30/2014 15:46:26
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/30/2014 15:56:39
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/30/2014 15:56:39
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/30/2014 15:56:40
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/30/2014 15:56:40
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/30/2014 15:56:40
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/30/2014 15:56:42
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/30/2014 15:56:43
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 04/30/2014 15:56:43
(Event String could not be retrieved)
......................... WSGPDC failed test systemlog
Test omitted by user request: VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)
CN=WSGPDC,OU=Domain Controllers,DC=WSG,DC=local and backlink on
CN=WSGPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WSG,DC=local
are correct.
The system object reference (frsComputerReferenceBL)
CN=WSGPDC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=WSG,DC=local
and backlink on CN=WSGPDC,OU=Domain Controllers,DC=WSG,DC=local are
correct.
The system object reference (serverReferenceBL)
CN=WSGPDC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=WSG,DC=local
and backlink on
CN=NTDS Settings,CN=WSGPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=WSG,DC=local
are correct.
......................... WSGPDC passed test VerifyReferences
Test omitted by user request: VerifyEnterpriseReferences
Test omitted by user request: CheckSecurityError
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : WSG
Starting test: CrossRefValidation
......................... WSG passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... WSG passed test CheckSDRefDom
Running enterprise tests on : WSG.local
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... WSG.local passed test Intersite
Starting test: FsmoCheck
GC Name: \\wsgpdc.WSG.local
Locator Flags: 0xe00001fd
PDC Name: \\wsgpdc.WSG.local
Locator Flags: 0xe00001fd
Time Server Name: \\wsgpdc.WSG.local
Locator Flags: 0xe00001fd
Preferred Time Server Name: \\wsgpdc.WSG.local
Locator Flags: 0xe00001fd
KDC Name: \\wsgpdc.WSG.local
Locator Flags: 0xe00001fd
......................... WSG.local passed test FsmoCheck
Test omitted by user request: DNS
Test omitted by user request: DNS
Computer Name: WSGPDC
DNS Host Name: wsgpdc.WSG.local
System info : Microsoft Windows Server 2003 (Build 3790)
Processor : x86 Family 6 Model 15 Stepping 11, GenuineIntel
List of installed hotfixes :
KB2079403
KB2115168
KB2121546
KB2124261
KB2229593
KB2264107
KB2296011
KB2345886
KB2347290
KB2360937
KB2378111
KB2387149
KB2393802
KB2412687
KB2416451
KB2419635
KB2423089
KB2440591
KB2443105
KB2443685
KB2476490
KB2476687
KB2478953
KB2478960
KB2478971
KB2481109
KB2483185
KB2485663
KB2492386
KB2497640
KB2497640-IE8
KB2503658
KB2503665
KB2506212
KB2506223
KB2507618
KB2507938
KB2508272
KB2508429
KB2509553
KB2510531-IE8
KB2510587
KB2511455
KB2524375
KB2524426
KB2530548-IE8
KB2535512
KB2536276
KB2536276-v2
KB2544521-IE8
KB2544893
KB2544893-v2
KB2555917
KB2559049-IE8
KB2562485
KB2564958
KB2566454
KB2567053
KB2567680
KB2570222
KB2570947
KB2571621
KB2572069
KB2584146
KB2585542
KB2586448-IE8
KB2592799
KB2598479
KB2601626
KB2603381
KB2604078
KB2607712
KB2616676
KB2618444-IE8
KB2618451
KB2620712
KB2621146
KB2621440
KB2624667
KB2631813
KB2633171
KB2638806
KB2639417
KB2641653
KB2641690-v2
KB2644615
KB2645640
KB2646524
KB2647170
KB2647516-IE8
KB2653956
KB2655992
KB2656358
KB2656376
KB2656376-v2
KB2659262
KB2660465
KB2661254
KB2675157-IE8
KB2676562
KB2685939
KB2686509
KB2691442
KB2698032
KB2698365
KB2699988-IE8
KB2705219
KB2707511
KB2709162
KB2712808
KB2718523
KB2718704
KB2719985
KB2722913-IE8
KB2724197
KB2727528
KB2731847
KB2742604
KB2744842-IE8
KB2748349
KB2749655
KB2753842
KB2753842-v2
KB2758857
KB2761226
KB2761465-IE8
KB2770660
KB2772930
KB2778344
KB2779030
KB2780091
KB2792100-IE8
KB2797052-IE8
KB2799329-IE8
KB2799494
KB2803821
KB2803821-v2
KB2807986
KB2808735
KB2809289-IE8
KB2813170
KB2813345
KB2817183-IE8
KB2820197
KB2820917
KB2829361
KB2829530-IE8
KB2833949
KB2834886
KB2838727-IE8
KB2839229
KB2845187
KB2846071-IE8
KB2847204-IE8
KB2847311
KB2849470
KB2850851
KB2850869
KB2859537
KB2862152
KB2862330
KB2862335
KB2862772-IE8
KB2864058
KB2864063
KB2868038
KB2868626
KB2870699-IE8
KB2876217
KB2876315
KB2876331
KB2879017-IE8
KB2883150
KB2892076
KB2893294
KB2893984
KB2898715
KB2898785-IE8
KB2898860
KB2900986
KB2901115
KB2909210-IE8
KB2909921-IE8
KB2914368
KB2916036
KB2922229
KB2923392
KB2925418-IE8
KB2929961
KB2930275
KB2936068-IE8
KB923561
KB925398_WMP64
KB925876
KB925902-v2
KB927891
KB929123
KB932168
KB933854
KB936357
KB938127
KB938759-v4
KB941569
KB942831
KB943055
KB943729
KB944653
KB946026
KB948496
KB950762
KB950974
KB952004
KB952069
KB952954
KB953298
KB954155
KB954550-v5
KB956263
KB956572
KB956802
KB956844
KB958469
KB958644
KB959426
KB960803
KB960859
KB961063
KB961118
KB961501
KB967715
KB967723
KB968389
KB969059
KB969883
KB970483
KB971029
KB971032
KB971513
KB971657
KB971737
KB972270
KB973507
KB973540
KB973815
KB973825
KB973869
KB973904
KB973917-v2
KB974112
KB974318
KB974392
KB974571
KB975025
KB975467
KB975558_WM8
KB975560
KB975562
KB975713
KB976323
KB977816
KB977914
KB978338
KB978542
KB978601
KB978695
KB978706
KB979309
KB979482
KB979687
KB979907
KB980232
KB980436
KB981322
KB982132
KB982632-IE8
KB982666
Q147222
Netcard queries test . . . . . . . : Passed
Per interface results:
Adapter : Server Local Area Connection
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : wsgpdc
IP Address . . . . . . . . : 192.168.1.2
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.1.1
Dns Servers. . . . . . . . : 192.168.1.2
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Passed
NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.
No remote names have been found.
WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{5995589E-FC82-4DD9-8A92-33B572B20DE3}
1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server '192.168.1.2' and other DCs also have some of the names registered.
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{5995589E-FC82-4DD9-8A92-33B572B20DE3}
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{5995589E-FC82-4DD9-8A92-33B572B20DE3}
The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Skipped
Note: run "netsh ipsec dynamic show /?" for more detailed information
The command completed successfully
Replication Summary Start Time: 2014-04-30 16:16:23
Beginning data collection for replication summary, this may take awhile:
Source DC largest delta fails/total %% error
WSGBDC >60 days 5 / 5 100 (8457) The destination server is currently rejecting replication requests.
Destination DC largest delta fails/total %% error
WSGPDC >60 days 5 / 5 100 (8457) The destination server is currently rejecting replication requests.
Experienced the following operational errors trying to retrieve replication information:
58 - wsgbdc.WSG.local
In the event viewer there are two errors in the Directory Service, Error ID 2089 and 1864 both regarding replication not taking place. -
Long DDIC Activation for Master Data Change During Transport
Good Morning Folks,
During transport of a change to a custom master data object to production, the data dictionary activation is taking a very long time and using a very large amount of space.
The change to the master data object was adding three additional navigational attributes. This master data is not time-dependant. The master data contains about 1.2 million records and has 49 active navigational attributes u2013 including the three new ones. The Data Dictionary activation is executing report SAPLRSDU for more than 8 hours and is using upwards of 52GB of temp filespace (of 92GB allocated) during this time. To the best of our knowledge, it looks as if it is trying to recreate or repopulate the /BIC/Pxxxx table of the master data. It looks like it's reading billions of records (probably the same 1.2 m records over and over.)
There are no errors in any logs that we can see.
Previous changes to this master data object have been successful, and reasonably fast. And the transport of this change from Dev to our QA environment was very fast.
We still need to get this change in, as well as additional changes that are dependant. Why would this take so long, and is there anything we can do to get this to run faster?
BTW: We are on 3.5 (but looking forward to NW7.)
Thanks, BrianBrian,
Usually adding nav attributes would mean that the X and y tables get regenerated...
Also do you notice reads only on the P-Table or other tables which have this object as well..?
If it is only the P Table - try refreshing the stats for the same... -
Transport classes and programs to another server
Except for transport routing and charm copy function, do we have other ways to do so?
for example copy or so forth.
best regards,
Blake LeHi Blake
SAP R/3 Correction and Transport System
Operating system level files in the transport process:
The SAP C program TP, requires a special file structure for the transport process. The file system is operating system dependent. TP uses a transport directory or file system, which is called /usr/sap/trans.
The /usr/sap/trans file system is generally NFS mounted form the development system to other systems unless a system is defined as a single system in the CTS pipeline. All the sub directories should have <SID>adm as the owner and sapsys as the group; and proper read, write and execute access should be given to owner and the group. The TP imports are always performed by <SID>adm.
The following are the subdirectories in /usr/sap/trans:
/data
/cofiles
/bin
/log
/actlog
/buffer
/sapnames
/tmp
/usr/sap/trans/data: holds the data of transport objects after they are released . The example of a data file is R904073.DEV. The extension DEV means the data file was released from the DEV or development system.
/usr/sap/trans/cofiles: The cofiles directory holds the command files for all change requests. These files are like a command or control files used to import the data files. The common directory for CTS system is /usr/sap/trans. After a change request is released from the source system , the data is exported immediately to the file system of the operating system. The SAP transport utility TP uses the cofile to transport a data file. The example of a file in cofiles directory is K904073.DEV.
/usr/sap/trans/bin: holds the most important file TPPARAM in the CTS system. TPPARAM file has all the information about the CTS systems in the CTS pipeline. TPPARAM file is the parameter file for the transport program TP and it is the common file for all the systems in the CTS pipeline. As you know already that /usr/sap/trans should be NFS mounted to all the systems in a CTS pipeline, TP program has access to the TPPARAM file from all the systems. The following is an example of typical TPPARAM file for five SAP systems in the CTS pipeline:
#@(#) TPPARAM.sap 20.6 SAP 95/03/28
Template of TPPARAM for UNIX #
First we specify global values for some parameters, #
later the system specific incarnation of special parameters #
global Parameters #
transdir = /usr/sap/trans/
dbname = $(system)
alllog = ALOG$(syear)$(yweek)
syslog = SLOG$(syear)$(yweek).$(system)
System spezific Parameters #
Beispiel T11 #
DEV/dbname = DEV
DEV/dbhost = sap9f
DEV/r3transpath = /usr/sap/DEV/SYS/exe/run/R3trans
QAS/dbname = QAS
QAS/dbhost = sap8f
QAS/r3transpath = /usr/sap/QAS/SYS/exe/run/R3trans
TRN/dbname = TRN
TRN/dbhost = sap17
TRN/r3transpath = /usr/sap/TRN/SYS/exe/run/R3trans
PRE/dbname = PRE
PRE/dbhost = sap19f
PRE/r3transpath = /usr/sap/PRE/SYS/exe/run/R3trans
PRD/dbname = PRD
PRD/dbhost = sap18f
PRD/r3transpath = /usr/sap/PRD/SYS/exe/run/R3trans
/usr/sap/trans/log: holds the entire log files, trace files and statistics for the CTS system. When the user goes to SE09 (workbench organizer) or SE10 (customizing organizer) transaction and opens the log for a transport, the log file for that transport will be read from /usr/sap/trans/log directory. Each change request should have a log file. Examples of log files are DEVG904073.QAS, DEVI904073.QAS and DEVV904073.QAS. The name of a log file consists of the names of the change request, the executed step, and the system in which the step was executed:
<source system><action><6 digits>.<target system>
Now we can analyze the above example DEVG904073. QAS. The <source system> = DEV, <action> = G or report and screen generation, <6 digits> = 904073 (these six digits numbers are exactly the same number as the six digits of the transport) and the <target system> = QAS
Possible values for <action> are:
A: Dictionary activation
D: Import of application-defined objects
E: R3trans export
G: Report and screen generation
H: R3trans dictionary import
I: R3trans main import
L: R3trans import of the command files
M: Activation of the enqueue modules
P: Test import
R: Execution of reports after put (XPRA)
T: R3trans import of table entries
V: Set version flag
X: Export of application-defined objects.
/usr/sap/trans/actlog: holds action log files. The example of an action file is DEVZ902690.DEV. The following are the contents of the file:
1 ETK220 u201C==================================================u201D u201C=================
=============================
1 ETK191 u201C04/30/1998u2033 Action log for request/task: u201CDEVK902690u2033
1 ETK220 u201C==================================================u201D u201C=================
=============================
1 ETK185 u201C04/30/1998 18:02:32u2033 u201CMOHASX01u2033 has reincluded the request/task
4 EPU120 Timeu2026 u201C18:02:32u2033 Run timeu2026 u201C00:00:00u2033
1 ETK193 u201C04/30/1998 18:02:33u2033 u201CMOHASX01u2033 owner, linked by u201CMOHASX01u2033 to u201CDEVK902691u2033
4 EPU120 Timeu2026 u201C18:02:33u2033 Run timeu2026 u201C00:00:00u2033
1 ETK190 u201C05/04/1998 11:02:40u2033 u201CMOHASX01u2033 has locked and released the request/task
1 ETK194 u201C05/04/1998 11:02:40u2033 **************** End of log *******************
4 EPU120 Timeu2026 u201C11:02:40u2033 Run timeu2026 u201C00:00:09u2033
~
~u201DDEVZ902690.DEVu201D 10 lines, 783 characters
/usr/sap/trans/buffer: transport buffer of the target systems; contains control information on which requests are to be imported into which systems and in what order the imports must occur. The /usr/sap/trans/buffer will have a directory for each system in the CTS pipeline. For example the buffer file for DEV system is /usr/sap/trans/buffer/DEV.
/usr/sap/trans/sapnames: holds information pertaining to transport requests for each system user. There are files for each user who released change requests from the system.
/usr/sap/trans/tmp: holds information about temporary data and log files. While the transport is occurring the Basis administrator can find a file that is related to the transport in the tmp directory; that file shows the exact status if the transport (What objects are being imported at that time).
Important SAP delivery class and table types and tables in the CTS process:
Delivery class
The delivery class defines who (i.e. the SAP system itself or the customer) is responsible for maintaining the table contents. In addition the delivery class controls how the table behaves in a client copy and an upgrade. For example when you select a SAP defined profiles to perform a client copy, certain tables are selected according to their delivery class. DD02L table can show what delevery class a table belongs to.
The following delivery classes exist:
A: Application table.
C: Customizing table, maintenance by customer only.
L: Table for storing temporary data.
G: Customizing table, entries protected against overwriting.
E: Control table.
S: System table, maintenance only by SAP.
W: System table, contents can be transported via own TR objects.
Table type
The table type defines whether a physical table exists for the logical table description defined in the ABAP/4 Dictionary and how the table is stored on the database.
The following are different table types in SAP:
Transparent Tables
There is a physical table on the database for each transparent table. The names of the physical table and the logical table definition in the ABAP/4 Dictionary are same. For every transparent table in SAP, there is a table in database. The business and application data are stored in transparent tables.
Structure
No data records exist on the database for a structure. Structures are used for the interface definition between programs or between screens and programs.
Append Structure
An Append structure defines a subset of fields which belong to another table or structure but which are treated as a separate object in the correction management. Append structures are used to support modifications.
The following table types are used for internal purposes, for example to store control data or for continuous texts:
Pooled table
Pooled tables can be used to store control data (e.g. screen sequences, program parameters or temporary data). Several pooled tables can be combined to form a table pool. The table pool corresponds to a physical table on the database in which all the records of the allocated-pooled tables are stored.
Cluster table
Cluster tables contain continuous text, for example documentation. Several cluster tables can be combined to form a table cluster. Several logical lines of different tables are combined to form a physical record in this table type. This permits object-by-object storage or object-by-object access. In order to combine tables in clusters, at least part of the keys must agree. Several cluster tables are stored in one corresponding table on the database.
Tables in CTS process:
TRBAT and TRJOB:
TRJOB and TRBAT are the major tables in the CTS process. After TP program has sent the event to the r3 system, RDDIMPDP checks table TRBAT in the target system to find out if there is an action to be performed. Mass activation, distribution, or table conversions are the examples of actions. If there is action to be performed, RDDIMPDP starts the appropriate program in the background task. RDDIMPDP then reschedules itself.
By checking table TRJOB, RDDIMPDP automatically recognizes if a previous step was aborted, and restarts this step. For each transport request , TP program inserts an entry into table TRBAT. If the return code 9999 in this table then the step is waiting to be performed. Return code 8888 indicates that the step is active and currently being processed. A return code of 12 or less indicates that the step is finished. In addition, TP inserts a header entry to let the RDDIMPDP program know to start processing. The column return code will therefore contain a B for begin. When RDDIMPDP is started, it sets the header entry to R(un), and starts the required program. When all the necessary actions are performed for all the transport requests, the column return code contains all the return codes received, and the column TIMESTAMP contains the finishing time. The header entry is set to F(inished). TP monitors the entries in TRBAT and TRJOB tables. When the header entry in TRBAT is set to finished. The entry in TRJOB is deleted.
Transport Tables SE06
TDEVC - Development classes
TASYS - Details of the delivery. Systems in the group that should automatically receive requests, have to be specified in table TASYS.
TSYST - The transport layers will be assigned to the integration systems. ( Define all systems)
TWSYS - Consolidation routes ( define consolidation path)
DEVL - Transport layers are defined here
In u201CConfiguring the CTS systemu201D section, We will learn more about the transport tables in SE06 transaction
Programs in the CTS process:
In the CTS table section we learned about the RDDIMPDP program. RDDIMPDP program needs to be scheduled in all the clients in an instance. It is recommended to schedule the RDDIMPDP as event driven.
RDDPUTPP and RDDNEWPP programs can be used to schedule RDDIMPDP program in the background.
The ABAP/4 programs that RDDIMPDP starts are determined by the transport step to be executed that is entered in the function field of table TRBAT.
Function Job Name Description of transport Steps
J RDDMASGL Activation of ABAP/4 dictionary objects
M RDDMASGL Activation of match codes and lock objects
S RDDDISOL Analysis of database objects to be converted
N RDDGENOL Conversion of database objects
Y RDDGENOL Conversion of matchcode tables
X RDDDICOL Export of AD0 objects
D RDDDIC1L Import of AD0 objects
E RDDVERSE Version management update during export
V RDDVERSL Version management update during import
R RDDEXECL Execution of programs for post - import processing
G RDDDIC3L Generation of ABAP/4 programs and screens
Version Management:
One of the important features of Workbench Organizer is Version Management. This feature works for all the development objects. Using the version management feature the users can compare and retrieve previous versions of objects.
Version management provides for comparisons, restore of previous versions, documentation of changes and assistance in the adjustment of data after upgrading to a new release. With the release of a change request, version maintenance is automatically recorded for each object. If an object in the system has been changed N times, it will have N delta versions and one active version. To display version management, for ABAPs use transaction SE38 and for tables, domains and data elements use SE11. The path to follow is Utilities -> Display version. Using version management the users can view existing version for previously created ABAP code, make changes to the code, compare code versions and restore original version of the code. Now the users will be restore previous versions without cut and paste steps of the past.
TP and R3trans program:
The basis administrator uses TP program to transport SAP objects from one system to another. TP is a C program delivered by SAP that runs independently of the R/3 system. TP program uses the appropriate files located in a common transport directory /usr/sap/trans. TP starts C programs, ABAP/4 programs and special operating system commands to its job. R3trans is one of the most important utility program called by TP. Before using the TP program, the basis administrator needs to make sure that the CTS system is setup properly and the right version of TP is running in the system. The TP program is located in the run time directory /usr/sap/<SID>/SYS/exe/run directory. It is automatically copied in the install process. A global parameter file TPPARAM that contains the databases of the different target systems and other information for the transport process controls TP. The global parameter file determines which R3trans is used for each system. If the parameter r3transpath is not defined properly then no export and import can be done. The basis administrator should make sure that the default value u201Cr3transpathu201D is properly defined. Later in this chapter we will learn more about TP and R3trans; also we are going to see how they are used.
Configuring the TPPARAM file:
Each time TP is started, it must know the location of the global parameter file. As we have seen before TPPARAM file should be in directory /usr/sap/trans/bin. The parameters in TPPARAM can either global (valid for each and every system in the cts pipeline) or local to one system. Th parameters are either operating system dependant (these parameters preceded by a keyword corresponding to the specific operating system) or database dependant (contain a keyword corresponding to a specific database system).
The global parameter file provides variables that can be used for defining parameters. The variables can be defined in format: $(xyz). The brackets can be substituted with the u201C\u201D-character if required.
The following pre-defined variables are available for the global parameter file:
$(cpu1): The CPU name can be sun or as4 for example. In heterogeneous networks this variable is very important.
$(cpu2): Acronym for the name of the operating system. The example for this variable can be
hp-ux, or sunos . This is an operating system specific variable.
$(dname): Used for the day of the week (SUN,MON,u2026.).
$(mday): Used for the day of the current month (01-31).
$(mname): Used for the name of the month (JANu2026DEC).
$(mon): Used for the Month (01-12).
$(system): R/3 System name.
$(wday): Day of the week (00-06, Sunday=00, Monday=01, Tuesday=02 and so on).
$(yday): Day of the current year (001-366). Using the number any day of the year can be chosen.
$(year): Year (Example:1998 or 1999).
$(syear): Short form of the year (two positions).
$(yweek): Calendar week (00-53). The first week begins with the first Sunday of the year.
For the database connection:
The transport environment also needs parameters to connect to the R/3 System database. As we know already the every instance in the R/3 CTS pipeline has its own database, therefore specific parameters should be defined for each database system. From dbtype parameter of RSPARAM file, TP program identifies the database system.
The two parameters u201Cdbnameu201D and u201Cdbhostu201D are required for ORACLE databases.
DBHOST: is the name of the computer on which the database processes execute. TCP/IP name of the host if NT is being used.
DBNAME: is the name of the database instance.
As of Release 3.0E, two new parameters have been introduced.
DBLOGICALNAME: The default value is $(system). The logical name that was used to install the database.
DBCONFPATH: The default value is $(transdir).
The parameters u201Cdbnameu201D and u201Cdbhostu201D are also used for INFORMIX databases in an installation:
DBHOST: Same as Oracle.
DBNAME: Name of the database instance, uppercase and lowercase are distinguished here.
INFORMIXDIR : u201C/informix/<SAPSID>u201D is the default value. Defines the directory namewhere the database software can be found.
INFORMIXSQLHOSTS: u201C$(informixdir)/etc/sqlhosts[.tli|.soc]u201Cis default value under Unix. The name of the SQLhosts file with its complete path is defined with this parameter.
INFORMIX_SERVER: u201C$(dbhost)$(dbname)shmu201D is the default value. The name of the database server may be specified for a local connect.
INFORMIX_SERVERALIAS: u201C$(dbhost)$(dbname)tcpu201Dis the default vlue. The name of the database server can be specified for a remote connect.
For Microsoft SQL Server database the two parameters u201Cdbnameu201D and u201Cdbhostu201D are also required. DBHOST: The TCP/IP name of the host on which the database is running.
DBNAME: The database instance name.
For DB2 in AS/400 only u201Cdbhostu201D is required.
DBHOST: System name of the host on which the database is running.
If theu201DOptiConnectu201D is used, the following line should be specified:
OPTICONNECT 1
For DB2/ AIX
The two parameters u201Cdbnameu201D and u201Cdbhostu201D are required
DBHOST: The host on which the database processes are running. It is the TCP/IP name of the host for Windows NT (As we have seen in the earlier examples).
DBNAME: Database instance name.
The DB2 for AIX Client Application Enabler Software must also be installed on the host on which tp is running.
ALLLOG: u201CALOGu201D $(syear) $(yweek)u201Dis the default value. This variable can be used in TPPARAM file to specify the name of a file in which tp stores information about every transport step carried out for a change request anywhere in the transport process. The file always resides in the log directory.
SYSLOG: u201CSLOG $(syear) $(yweek).$(system)u201D is the default value. This variable can be used to name a file in which tp stores information about the progress of import actions in a certain R/3 System. The file does not store information for any particular change request. The file always resides in the log directory.
tp_VERSION: Zero is the default value. If this parameter is set to not equal to zero, a lower version of tp may not work with this TPPARAM file. If the default value (zero) is set, the parameter has no affect.
STOPONERROR: (Numeric value) The default value is 9. When STOPONERROR is set to zero, tp is never stopped in the middle of an u201Cimportu201D or u201Cputu201D call. When STOPONERROR is set to a value greater than zero, tp stops as soon as a change request generates a return code that is equal to or greater than this value (The numeric value of the STOPONERROR parameter is stored in the variable BADRC). Change requests, which still have to be processed for the current step, are first completed. A u201CSYNCMARKu201D in the buffer of the R/3 System involved, sets a limit here. tp divides the value of this parameter between two internal variables. STOPONERROR itself is treated as a boolean variable that determines whether tp should be stopped, if the return code is too high.
REPEATONERROR (Numeric value too): The default value is 9. The REPEATONERROR parameter is similar to STOPONERROR. The difference is, REPEATONERROR specifies the return code up to which a change request is considered to be successfully processed. Return codes less than REPEATONERROR are accepted as u201Cin Orderu201D. Change requests that were not processed successfully stay in the buffer.
NEW_SAPNAMES: Default value is u201CFALSEu201D. A file is created for each user of the R/3 System group in the u201Csapnamesu201D subdirectory of the transport directory. Except some of the operating system,the name of the user is the name of the file. It is very important to remember hat the special characters or length of the file name could cause problems. If all the R/3 Systems in the transport group have at least Release level 3.0.; TP program is efficient to handle this problem. The user names are modified to create file names that are valid in all operating systems and the real user names are stored in a corresponding file.
Though we have seen so many parameters, for the minimum configuration the following two parameters are very important.
TRANSDIR: specifies the name of the common transport directory. The following is a typical example from TPPARAM of Unix as we have seen before.
transdir = /usr/sap/trans/
DBHOST: contains the name of the database host. In Windows NT environment, this is the TCP/IP host name. The following is an example in Unix:
DEV/dbname = DEV
DEV/dbhost = sap9f
DEV/r3transpath = /usr/sap/DEV/SYS/exe/run/R3trans
For TP, to control u2018Start and Stopu2019 command files and database in R/3 the following important parameters are specified in TPPARAM:
Parameters for the tp Function u201CPUTu201D: LOCK_EU (boolean) default value is u201CTRUEu201D. Though from version 3.1 onward the tp put command is used seldom in cts process still it is important to know how this parameter works. When u201Ctp putu201D is used, it changes the system change option . If the parameter is set to u201CFALSEu201D nothing gets changed. If the parameter is set to u201CTRUEu201D, the system change option is set to u201CObjects cannot be changedu201D at the beginning of the call, and gets changed back to its previous value at the end of the call. The u201Ctp putu201D command will give the exact status of the locking mechanism.
LOCKUSER (used as boolean value): Default value is u201CTRUEu201D. This parameter is about the user login while tp put call is executed. If this parameter is set to u201CFALSEu201D, no locking mechanism for the users takes affect. If this parameter is defined as u201CTRUEu201D then a character is set in the database level; so only DDIC and SAP* can log on to the system. Users that have already logged on are not affected (this is a reason for activating the parameters STARTSAP and STOPSAP). The charactertor is removed at the end of the call, and all the users can log on to the SAP R/3 System again.
STARTSAP: Default value is u201D u201C.or u201CPROMPTu201D for Windows NT . This parameter is used by TP to start an R/3 System. It is not necessary for the clients to make tp start and stop R/3 system..
STOPSAP: Default value is u201D u201Cor u201CPROMPTu201D for Windows NT. TP uses this parameter to stop an R/3 System.
STARTDB: Default value is u201D u201C. TP uses the value of this parameter to start the database of an R/3 System.
The parameter is not active under Windows NT.
STOPDB: Default value is u201D u201C. TP uses the value of this parameter to stop the database of an R/3 System.
This parameter is not active under Windows NT.
The above parameters in UNIX can be used as following:
STARTSAP = startsap R3
STOPSAP = stopsap R3
STARTDB = startsap db
STOPDB = stopsap db
In Windows NT:
STARTSAP =
$(SAPGLOBALHOST)\sapmnt\$(system)\sys\exe\run\startsap.exe
R3 <SID> <HOST NAME> <START PROFILE>
STOPSAP =
$(SAPGLOBALHOST)\sapmnt\$(system)\sys\exe\run\stopsap.exe
R3 <SID> <HOST NAME> <INSTANCE> <PROFILE PATH + Instance profile>
The parameters STARTDB and STOPDB are not active under Windows NT.
Parameters for the tp function u201CCLEAROLDu201D
DATALIFETIME (Numeric): Default value is u201C200u2033. When the data file has reached a minimum age, it is moved to the subdirectory old data with tp check. tp clearold all. The life span of the data files in the data sub directory can be set in days with this all, parameter.
OLDDATALIFETIME (Numeric): Default value is u201C365u2033. When a file located in the olddata subdirectory is no longer needed for further actions of the transport system and has reached a minimum age, it is removed with tp check.all, tp clearold all. The minimum age in days can be set with this parameter.
COFILELIFETIME (Numeric): Default value is u201C365u2033. This parameter is used just like DATALIFETIME parameter.
LOGLIFETIME (Numeric): Default value is u201C200u2033. This parameter applies to the life span of the log files. When the log files in log subdirectory is no longer needed for the transport system and has reached a minimum age, it is deleted with the calls tp check.all, tp clearold all. The minimum age in days can be defined with this parameter.
The Three Key Utilities of the CTS system (TP, R3trans and R3chop):
TP: Earlier in this chapter we have seen the objectives of TP. The TP transport control program is a utility program that helps the user to transport objects from one system to another. TP program is the front-end for the utility R3trans. TP stands for u201CTransports and Putsu201D. To make the TP work successfully the CTS system needs to be correctly configured. The following steps are very important for TP to run properly.
The transport directory /usr/sap/trans must be installed and NFS mounted to all the systems in the CTS pipe line.
RDDIMPDP program must be running (event driven is recommended) in each client. RDDIMPDP can be scheduled in the background by executing RDDNEWPP or RDDPUTPP. Use the tp checkimpdp <sap sid> command in /usr/sap/trans/bin directory as <sid>adm user to check RDDIMPDP program.
Use the tp connect <sap sid> command in /usr/sap/trans/bin directory to see whether the tp program is connecting to the database successfully or not. To run TP command the user has to logon as <sid>adm in source or target system.
The R/3 Systems in the CTS pipeline must have different names.
The Global CTS Parameter File TPPARAM must be correctly configured.
The source system (for the export) and target system ( for the import) must have at least two background work processes. TP always schedules the C class job, so if all the background jobs are defined as A class job then there will be problems in transport steps.
Important Tips :.It is always better to have the up to date TP version installed in your system. A user can ftp a current version of TP from SAPSERV4 of SAP. Though R3trans and other utility programs can be used to do the transport, it is recommended to use TP whenever possible for the following reasons..
The exports and imports are done separately using TP program. For example: when a transport is released from the system, the objects are exported from the source database to the operating system and then the import phase starts to transport those objects to the target system.
TP takes care of the order of the objects. The order, that was followed to export the objects; the same order will be followed to import them to the target database.
The TP command processes all change requests or transports in the SAP system buffer that have not yet been imported successfully. All the import steps are executed automatically after TP calls R3trans program to execute the following necessary steps:
Dictionary Import: ABAP/4 dictionary objects will be imported in this step.
Dictionary Activation: Name tabs or runtime descriptions will be written inactively. The R/3 system keeps running until the activation phase is complete. The enqueue modules are the exceptions in the running phase. After the activation of new dictionary structure the new actions are decided to get the runtime objects to the target system.
Structure conversion: If necessary the table structure is changed in this phase.
Move Nametabs: The new ABAP/4 Dictionary runtime objects which were inactive up to now are moved into the active runtime environment in this process. The database structures are adjusted accordingly. From the first step to the Main import step inconsistencies can occur to the R/3 system. After the main import phase all the inconsistency ca be solved.
Main import with R3trans: All the data are imported completely and the system comes to a consistent state.
Activation of enqueue-objects: The enqueue-objects cannot be activated in the same way as the objects of the ABAP/4 Dictionary, so they have to be activated after the main import in this step. They are then used directly in the running system.
Structure Conversion of match codes, Import application defined objects, versioning and execution of user defined activities are some of the steps after activation of enqueue-objects. The next step is generation of ABAP/4 programs and screens, where all the programs and screens associated with the change request are generated. When all the import steps are completed successfully, the transport request is removed from the import buffer.
It is recommended by SAP to schedule regular periods for imports into the target system (e.g. daily, weekly or monthly). Shorter periods between imports are not advisable. The transport to production should not be done in the off hours when the users are not working
TP can be started with different parameters. The u201Ctp helpu201D command can help user to generate a short description about the use of the command.
The following are the some important commands of TP:
For export:
tp export <change request>: The complete objects in the request from the source system will be transported. This command also used by SAP System when it releases a request.
tp r3e <change request>: R3trans export of one transport request.
tp sde <change request>: Application defined objects in one transport request can be exported.
tp tst <change request> <SAP system >: The test import for transport request can be done using this command.
tp createinfo <change request>: This command creates a information file that is automatically done during the export.
tp verse <request>: This command creates version creates versions of the objects in the specified request.
To Check the transport buffer, global parameter file and change requests:
tp showbuffer <sid>: Shows all the change requests ready to be imported to the target system.
tp count <sid>: Using this command users can find out the number of requests in the buffer waiting for import.
tp go <sid>: This command shows the environment variables needed for the connection to the database of the <sid> or target system.
tp showparams <sid>: All the values of modifiable tp parameters in the global parameter file. The default value is shown for parameters that have not been set explicitly.
To import the change requests or transports:
tp addtobuffer <request>.<sid>: If a change request is not in the buffer then this command is used to add it to the buffer, before the import step starts.
tp import all <sid>: This command imports all the change requests from the buffer to the target system.
tp put <sid>: The objective of this command is same as u201Ctp import all <sid>u201D, but this command locks the system. This command also starts and stops the SAP system, if the parameters startsap and stopsap parameters are not set to u201D u201C.
tp import <change request> <sid>: To import a single request from the source system to target system.
tp r3h <change request>| all <sid>: Using this command user can import the dictionary structures of one transport or all the transport from the buffer.
tp act <change request>|all <sid>: This command activates all the dictionary objects in the change request.
tp r3i <change request> | all <sid>: This command imports everything but dictionary structures of one.
tp sdi <change request>|all <sid>: Import application-defined objects.
tp gen <change request>|all <sid>: Screen and reports are generated using this command.
tp mvntabs <sid>: All inactive nametabs will be activated with this command.
tp mea <change request>|all <sid>: This command will activate the enqueue modules in the change request.
When you call this command, note the resulting changes to the import sequence.
Additional tp utility options:
tp check <sid>|all (data|cofiles|log|sapnames|verbose): User uses this command to find all the files in the transport directory that are not waiting for imports and they have exceeded the minimum time specified using the COFILELIFETIME, LOGFILELIFETIME, OLDDATALIFETIME and DATALIFETIME parameters of TPPARAM file.
tp delfrombuffer <request>.<sid>: This command removes a single change request from the buffer. In case of TMS, the request will be deleted from the import queue.
tp setstopmark <sid>: A flag is set to the list of requests ready for import into the target system. When the user uses the command tp import all <sapsid> and tp put <sapsid>, the requests in front of this mark are only processed. After all the requests in front of the mark have been imported successfully, the mark is deleted.
tp delstopmark <sid>: This command deletes the stop mark from the buffer if it exists.
tp cleanbuffer <sapsid>: Removes all the change requests from the buffer that are ready for the import into the target system.
tp locksys <sid>: This command locks the system for all the users except SAP* and DDIC. The users that have already logged on are not affected by the call.
tp unlocksys <sid>: This command unlocks the system for all the users.
tp lock_eu <sid>: This command sets the system change option to u201Csystem can not be changedu201D tmporarily.
tp unlock_eu <sid>: This command unlocks the system for all the changes.
tp backupall <sid>: This command starts a complete backup using R3trans command. It uses /usr/sap/trans/backup directory for the backup.
tp backup delta <sid>: Uses R3trans for a delta backup into /usr/sap/trans/backup directory.
tp sapstart <sid>: To start the R/3 system.
tp stopsap <sid>: To stop the R/3 system.
tp dbstart <sid>: To start the database.
tp dbstop <sid>: To stop the database.
Unconditional modes for TP: Unconditional modes are used with the TP program and these modes are intended for the special actions needed in the transport steps. Using unconditional mode user can manipulate the rules defined by the workbench organizer. The unconditional mode should be used when needed, otherwise it might create problems for the R/3 system database. Unconditional mode is used after the letter u201CUu201D in the TP command. Unconditional mode can be a digit between 0 to 9 and each has a meaning to it. The following is a example of a import having unconditional mode.
tp import devk903456 qas client100 U12468
0: Called a overtaker; change request can be imported from buffer without deleting it and then uncoditional mode 1 is used to allow another import in the correct location.
1: If U1 is used with the export then it ignores the correct status of the command file; and if it is used with import then it lets the user import the same change request again.
2: When used with tp export, it dictates the program to not to expand the selection with TRDIR brackets. If used in tp import phase, it overwrites the originals.
3: When used with tp import, it overwrites the system-dependant objects.
5: During the import to the consolidation system it permits the source systems other than the integration system.
6: When used in import phase, it helps to overwrite objects in unconfirmed repairs.
8: During import phase it ignores the limitations caused by the table classification.
9: During import it ignores that the system is locked for this kind of transport.
R3trans: TP uses R3trans program to transport data from one system to another in the CTS pipeline. efficient basis administrator can use R3trans directly to export and import data from and into any SAP systems. Using this utility transport between different database and operating system can e done without any problems. Different versions of R3trans are fully compatible with each other and can be used for export and import. The basis administrator has to be careful using R3trans for different release levels of R/3 software; logical inconsistency might occur if the up to date R3trans is not used for the current version of R/3 system.
The syntax for using the control file is following:
R3trans [<options>] <control file> (several options used at the same time; at least one option must be there)
For example: R3trans u2013u 1 u2013w test.log test
In the above example a unconditional mode is used, a log file u201Ctest.logu201D file is used to get the log result and a control file u201Ctestu201D, where the instructions are given for the R3trans to follow. The user needs to logon as <sid>adm to execute R3trans.
The following options are available for the R3trans program:
R3trans -d : This command is used to check the database connection .
R3trans -u <int>: Unconditional mode can be used as we have seen in the above example.
R3trans -v : This is used for verbose mode. It writes additional details to the log file
R3trans -i <file>: This command directly imports data from data file without a control file.
R3trans -l <file>: This provides output of a table of contents to the log file.
R3trans -n : This option provides a brief information about new features of R3trans.
R3trans u2013t: This option is used for the test mode. All modifications in the database are rolled back.
R3trans -c <f1> [<f2>]: This command is used for conversion. The <f1> file will be copied to <f2> file after executing a character set conversion to the local character set.
Important tips: Do not confuse the backup taken using R3trans with database backup. The backups taken using R3trans are logical backups of objects. In case something happens to the SAP system these backups can not be used for recovery. R3trans backups can be only used to restore a copy of a particular object that has been damaged or lost by the user.
R3trans -w <file>: As we have seen in the above example this option can be used to write to a log file. If no file is mentioned then trans.log is default directory for the log.
R3trans also can be used for the database backup.
R3trans u2013ba: This command is used for a complete backup. we will see in the next paragraph how to use
the control file for the backup.
R3trans u2013bd: This command is used for a delta backup if the user does not want a complete backup.
R3trans u2013bi: This option will display backup information.
The following are some of the examples of control files:
We have already learned how to use a command for the logical backup of the objects in the database. To get a complete backup the following example control file can be used.
backup all
file = /usr/sap/trans/backall
The option u201Cfile = u2026u201D is the name of the directory into which the data files are to be written. If you are taking a complete backup of DEV system then the backup file is going to look like u201CDEV.A000.bcku201D the next complete
Reward if useful
Regards
divya -
Allocation of Cost based on Match for 2 Dimensions
Hi Experts,
We are running an allocation where we assign an expense account balance (transportation costs) based on the combination of the dimensions entity and country. Please see the attached for a full example.
A brief example:
ORIGINAL DATA
Entity: Country AI Units (Currency)
1120 Holland AI_01 50
1120 Holland AI_03 30
1120 France AI_02 10
PRICING DATA
Entity: Country USD
1120 Holland 8
1120 France 10
DESIRED RESULT
1120 Holland AI_01 (50*8)=400
1120 Holland AI_03 (30*8)=240
1120 France AI_02 ((10*10)=100
ACTUAL RESULT
1120 Holland AI_01 (50+30) *8=640
1120 Holland AI_03 (50+ 30)*8=640
The original data is multiplied by a "pricing table" data that resides in a statistical account with similar dimensions for Entity and Country. Based on the match between Entity and Country between the data and country we assign the cost.
Issue is that other dimensions e.g. AI or other should be ignored for this calculation and the postings occur as they were originally. However the actual result based on the script below is duplicating data
Any ideas?
Thanks in advance
Eyal Feiler
SCRIPT USED
*RUNALLOCATION
*FACTOR=USING*1
*DIM CURRENCY WHAT=KL_Q ; WHERE=USD; USING=USD;
*DIM COUNTRY WHAT=[ALLOCATION]="y" ; WHERE=<<<; USING=<<<;
*DIM ACTIVE_INGREDIEN WHAT=[AI_ALLOCATION]="X"; WHERE=[AI_ALLOCATION]="X"; USING=AI_NONE;
*DIM ACCOUNT WHAT=411113; WHERE=612313; USING=411113;
*DIM AUDITID WHAT=AD3000; WHERE=AD5130; USING=AD4130;
*ENDALLOCATION
*COMMITVadim,
Again as before this helped us greatly!
Another question if I may:
2) The next step of the calculation is after we search for a price
based on the entity/country match, if one is not found we go to a second
pricing table and select based entity and property of the country (e.g. a
region) that has a new price.
This means that we could have a conflict between the 2 tables. e.g.
in the first table we find a match between Entity and country = France or
country = Holland.
Now when there's an entry = Greece there's no match in table 1 and
we go to table 2 to select the Europe price.
Europe price will now override the first 2 rows from table 1. How can we build this?
One thought is to first perform the select on table 2 (region) and
then override with (table 1) only where it's found?
Thoughts?
Thanks
Eyal -
Crystal Reports logon issue across firewall - Transport error:communication
Hi,
We are facing an error when we try to logon to the BO server using the crystal reports tool (Crystal Reports Enterprise XI Release 2 ) outside the firewall. The login is working fine when inside the firewall. The BO server is on a unix box within the customer network and we are trying to login from a PC (using Crystal Reports Enterprise XI Release 2) which is outside that network. The following are the errors we get when trying to logon using authentication as "Enterprise" and system name as "fully qualified server name:6400"
1. Without including any IP addresses in the PC host file we get "Transport error:communication failure" on login.
2. When I included the IP and name of the BO server in the PC host file (xx.xx.xx.xx host name) we get an error - "CMS host 'xxxx' address was resolved properly,but cannot be reached to establish a CMS connection.Verify your router/firewall allows communication on port 6400."
(The IP address I include in the PC host file is the actual IP address of the BO server)
3. I know we have natted IP addresses.. and the IP address of the BO server appears to be different when I do a ping to the BO server from outside the customer network i.e from the external PC. When I include the IP address in the host file (which I get from the ping <servername> outside the customer network from my PC) I get "Transport error:communication failure".
The port 6400 has been opened in the firewall. We are able to login to the CMC link and the Info view without any issues.
It will be great to get some advise on this as it has become a high priority issue in our workspace now.
Thanks,
ReetiHi All,
I had a breakthrough in logging to BOX1R2 Crystal Reports client outside the firewall. The following was done in our case:
1. Open the port 6400 on the server to allow traffic from outside the firewall.
2. Add the following command at the end in the cmsLAUNCH command line in ccm.config (ours is a BO server on Sun OS)
-port FQDN:6400 -requestport XXXX
The -port parameter was explicitly specified to make CMS explicitly listen on port 6400.
The -requestport parameter was added to configure the server to register a fixed port (which has external access) with the CMS rather than letting it choose a dynamically selected one...so XXXX can be any port which is not allocated to any app and is also open in the firewall)
Thanks,
Reeti
Maybe you are looking for
-
How can I use two Ipods on one computer.
I was wondering if it is possible to use 2 Ipods on one computer without having to reload all of the music to the new library.
-
I can't view PDF files in firefox anymore. == This happened == Every time Firefox opened == after updating firefox
-
Dear Friends , we have a portal and the users are maintained in R/3 that means UME is R/3 . Now when i have to give the access to the users to use ESS applications they are not bale to view ESS role since the portal is mapper to client where the user
-
I have a folder of about 4GB of files that I would like to burn to DVD. I have tried using Toast to no avail. Is there a simply free way of doing this, like with disk utility for instance, that will allow the files to be read on this computer as well
-
Collection Data Form in invisible mode.
Hi, We are using zcm 10.3 installed on SLES 11. Our clients are XP SP3. I have configured a collection data form with autofill and checked "Invisible mode for autofill only" In the autofill settings I have entered a environment variable. I have confi