Cleaning Up the Transport Directory

Dear All
I want to clear the old files from the trans directory, for the same, i exectute the command on Dos prompt,in
Windows
in BIN folder
tp check all
it generate following error
tp version is :- 372.04.57 (release 700, unicode enabled)
kernel release 700
This is tp version 372.04.57 (release 700, unicode enabled)
E-TPSETTINGS could not be opened.
EXIT
Error in TPSETTINGS: transdir not set.
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0208
tp finished with return code: 208
meaning:
error in transportprofil (param missing, unknown,...)
the Transport tool setting, the parameter
TRANSIDR is set
ides\sapmnt\trans &
DIR_TRANS value is
ides\sapmnt\trans
so please suggest me How to Cleaning Up the Transport
Directory
Thanks
Ganesh

Hi Ganesh,
Please go through the below links.
Import of a request failing : ERROR: connect failed due to DbSL load lib fa
how to add request in the buffer
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/tp-finished-with-return-code-208-1433190
http://www.sapfans.com/forums/viewtopic.php?f=12&t=67602
Re: Import of a request failing : ERROR: connect failed due to DbSL load li
-Srini

Similar Messages

Easiest way to upload a transport file in the transport directory.

Hello all,
Do you know what is the procedure to upload a transport file in the transport directory in the process of manually installing OSS Notes?
Thanks in advance for your help,
Luis

Hi Luis,
Try to go through transaction SNOTE for that.
You can check also http://scn.sap.com/blogs/tyronemapp/2012/05/08/how-to-manually-import-transports-into-sap-without-using-command-line-tp , a nice blog post from Mapp Tyrone on the subject.
Take care,
Ricardo

App Server Does not recognize the transport Directory

We have added a new server in the production system , but this server is not able to recognize the transport directory ,
In the instace profile , this parameter is set as below
DIR_TRANS =
bp1tulap139\sapmnt\trans
When i check the profile it throws a warning
W:DIR_TRANS directory
bp1tulap139\sapmnt\trans does not exist
Even the transport Directory
bp1tulap139\sapmnt\trans
is mounted on the server but still I am getting this error .
Please help

Oh man - that is Windows Security basics.
I am wondering how people can try to install and administrate enterprise level applications without this knowledge.
you may try to create SAPSERVICE<SID> as a local user on the machine where the transport directory is stored on and give it the same password on this machine. After that add it to the local SAP_LocalAdmin group.
After that the access should work (if both servers are member of the same workgroup).
peter

Change the Transport Directory.

Hi everybody, We have I system installed (S01) and we have just installed a new one (S02), we want to be able to trasnport from the system S01 to the system S02. What I have to do in order to do that?
I read that the systems have to have the same Transport Directory. And I checked with AL11 and the values for the DIR_TRANS parameter are the following for each system:
system S01 -> DIR_TRAN ->
S01\sapmnt\trans
system S02 -> DIR_TRAN ->
S02\sapmnt\trans
I tried to change the DIR_TRANS parameter with the transaction RZ10, but in S02 we don't have any profile.
Cuold you please help me to do that?
Thanks and Regards.

Hi,
read that the systems have to have the same Transport Directory.
not neccesary to have tarnsport directory, it depends upon scenario.
Pls follow the below link for configuring stms configuration.
bbs.cenet.org.cn/UploadImages/200581112435749207.pdf
Also check the below link
Common tranport directory on Windows local installation
Thanks,
Anil

I want to change the transport directory

Hello gurus,
I want to change the tranport directory in all our systems. Please advise me how to do it.
I really appreciate your help.
Regards,
N.S

Hi N.S,
How about :
http://help.sap.com/saphelp_47x200/helpdata/en/d5/10b4496f0f11d2b41a006094b9ea64/frameset.htm
is it common transport directory ?
To change the common transport directory configuration, you can
first go to transaction AL11 of one of your system, for example, PRD.
Change the 'DIR_TRANS' parameter, so that it points to the directory that you want to change
Then go to STMS, choose 'System Overview' button to display systems
of your transport domain. Double click PRD, with 'Transport
Tool' tab, click 'Display <-> Change' button, you can change the
'transdir' value.
Please make sure it is equal to the same configuration of 'DIR_TRANS'.
Repeat the above steps on your other system. Make sure the configurations
of 'transdir' and 'DIR_TRANS' are the same as that on the PRD system.
cheers,
Vincent

How to clean up the Actice Directory users and account?

Hi,
In my workplace we inherited a system which used to be based on Small Business Server, and the Active Directory is filled with User Groups and Containers that the SBS creates itself.
What is a good rule of thumb/ strategy to use, in order to get rid of the User Groups, Containers and Users that have been created by SBS previously?
The current structure results in extremely weird behavior applying only a bunch of GPOs to a some users and not to others. I believe this happens due to the extremely complicated structure (which is not needed anymore as we migrated to pure Windows Server
environment).
Suggestion, or articles would be extremely welcome.

Hi theotheisempre,
if you really had no more SBS Server in your infrastructure, and you also can confirm that there is no Service that used the AD Groups migrated from the SBS anymore, you can remove it. We did this many times and this was very easy. Main Thing is that you make
sure that you can remove all the Groups / structure step by step from the old SBS environment. On the other Hand, if your SBS is still in use, don't remove the OU structure nor the Groups.
While saying that I read about your GPO issue. That does not Sound like a problem related on the SBS OU structure. Please check your policy links, filters and inheritance instead.
Kind regards,
Martin

[SOLVED] Files in the /tmp directory are being deleted

Hi,
I've been using Arch Linux for four weeks, but have now come across a problem which I can't fix after trying to search for a solution (and also checking to see if anyone also had the same problem). I would appreciate any help you can give.
A few days ago the web browsers I use (chromium and opera) lost their profile settings, and I had to set the profiles. This kept happening and the indicator of the problem was that I use profile-sync-daemon for both web browsers, which uses the /tmp directory. I then started noticing that a file I created in /tmp disappeared which pointed me to the fact that something was cleaning up the /tmp directory (this seems to happen hourly).
A quick search led me to systemd-tmpfiles and the /usr/lib/tmpfiles.d/tmp.conf file. I have not modified the file, and if I have read it correctly only files in the /tmp directory that are more than 10 days old are deleted. I boot every day, so no files should be deleted by systemd-tmpfiles (unless I've misunderstood tmpfiles.d).
Here is the tmp.conf file anyway:
$ cat /usr/lib/tmpfiles.d/tmp.conf
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
# See tmpfiles.d(5) for details
# Clear tmp directories separately, to make them easier to override
d /tmp 1777 root root 10d
d /var/tmp 1777 root root 30d
# Exclude namespace mountpoints created with PrivateTmp=yes
x /tmp/systemd-private-*
x /var/tmp/systemd-private-*
X /tmp/systemd-private-*/tmp
X /var/tmp/systemd-private-*/tmp
The /etc/tmpfiles.d directory is empty, so /usr/lib/tmpfiles.d is the only location for the tmpfiles.d config files:
$ ls /etc/tmpfiles.d/
$
Here is the list of packages I upgraded/installed for the last few days. systemd 207-3 seems the likeliest candidate, but I have not come across any reports about the problem I am having.
[2013-09-17 19:30] [PACMAN] Running 'pacman -Syu'
[2013-09-17 19:30] [PACMAN] synchronizing package lists
[2013-09-17 19:30] [PACMAN] starting full system upgrade
[2013-09-17 19:34] [PACMAN] upgraded bluez-utils (5.7-1 -> 5.8-1)
[2013-09-17 19:34] [PACMAN] upgraded cogl (1.14.0-4 -> 1.14.0-5)
[2013-09-17 19:34] [PACMAN] upgraded dbus (1.6.12-1 -> 1.6.14-1)
[2013-09-17 19:34] [PACMAN] upgraded dialog (1.2_20130523-2 -> 1.2_20130902-1)
[2013-09-17 19:34] [PACMAN] installed efivar (0.6-1)
[2013-09-17 19:34] [PACMAN] upgraded efibootmgr (0.6.0-3 -> 0.6.0.138.1132342-1)
[2013-09-17 19:34] [ALPM-SCRIPTLET] Generating locales...
[2013-09-17 19:34] [ALPM-SCRIPTLET] en_GB.UTF-8... done
[2013-09-17 19:34] [ALPM-SCRIPTLET] Generation complete.
[2013-09-17 19:35] [PACMAN] upgraded glibc (2.18-3 -> 2.18-4)
[2013-09-17 19:35] [PACMAN] upgraded gnome-desktop (1:3.8.3-2 -> 1:3.8.4-1)
[2013-09-17 19:35] [PACMAN] upgraded gnome-color-manager (3.8.2-1 -> 3.8.3-1)
[2013-09-17 19:35] [PACMAN] upgraded gnome-settings-daemon (3.8.4-2 -> 3.8.5-1)
[2013-09-17 19:35] [PACMAN] upgraded gnome-control-center (3.8.4.1-2 -> 3.8.5-1)
[2013-09-17 19:35] [PACMAN] upgraded gnome-themes-standard (3.8.3-1 -> 3.8.4-1)
[2013-09-17 19:35] [PACMAN] upgraded libpng (1.6.3-1 -> 1.6.5-1)
[2013-09-17 19:35] [PACMAN] upgraded libusbx (1.0.16-2 -> 1.0.17-1)
[2013-09-17 19:35] [PACMAN] upgraded linux-firmware (20130725-1 -> 20130903-1)
[2013-09-17 19:35] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-09-17 19:35] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> Starting build: 3.11.1-1-ARCH
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> Starting build: 3.11.1-1-ARCH
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-09-17 19:35] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-09-17 19:35] [PACMAN] upgraded linux (3.10.10-1 -> 3.11.1-1)
[2013-09-17 19:35] [PACMAN] upgraded openssh (6.2p2-1 -> 6.3p1-1)
[2013-09-17 19:35] [PACMAN] upgraded orc (0.4.17-1 -> 0.4.18-1)
[2013-09-17 19:35] [ALPM-SCRIPTLET]
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> The file /etc/sysctl.conf has been removed from this
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> package, as all its settings are now kernel defaults.
[2013-09-17 19:35] [ALPM-SCRIPTLET]
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> If you had customized it, you need to rename it as
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> /etc/sysctl.d/99-sysctl.conf since from version 207 on
[2013-09-17 19:35] [ALPM-SCRIPTLET] ==> systemd only applies settings from /etc/sysctl.d/* .
[2013-09-17 19:35] [ALPM-SCRIPTLET]
[2013-09-17 19:35] [PACMAN] upgraded procps-ng (3.3.8-2 -> 3.3.8-3)
[2013-09-17 19:35] [PACMAN] upgraded raptor (2.0.9-2 -> 2.0.10-2)
[2013-09-17 19:35] [PACMAN] upgraded xorg-xinput (1.6.0-1 -> 1.6.1-1)
[2013-09-17 19:36] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-dsana/PKGDEST.u70/profile-sync-daemon-5.40.1-1-any.pkg.tar.xz'
[2013-09-17 19:36] [PACMAN] upgraded profile-sync-daemon (5.40-1 -> 5.40.1-1)
[2013-09-18 20:35] [PACMAN] Running 'pacman -Syu'
[2013-09-18 20:35] [PACMAN] synchronizing package lists
[2013-09-18 20:35] [PACMAN] starting full system upgrade
[2013-09-18 20:35] [ALPM] warning: /etc/systemd/journald.conf installed as /etc/systemd/journald.conf.pacnew
[2013-09-18 20:35] [ALPM-SCRIPTLET] ==> systemd 205 restructures the cgroup hierarchy and changes internal
[2013-09-18 20:35] [ALPM-SCRIPTLET] protocols. You should reboot at your earliest convenience.
[2013-09-18 20:35] [ALPM-SCRIPTLET] ==> The "timestamp" hook for mkinitcpio no longer exists. If you used
[2013-09-18 20:35] [ALPM-SCRIPTLET] this hook, you must remove it from /etc/mkinitcpio.conf. A "systemd"
[2013-09-18 20:35] [ALPM-SCRIPTLET] hook has been added which provides this functionality, and more.
[2013-09-18 20:35] [PACMAN] upgraded systemd (204-3 -> 207-3)
[2013-09-18 20:35] [PACMAN] upgraded systemd-sysvcompat (204-3 -> 207-3)
[2013-09-18 20:35] [PACMAN] upgraded udisks2 (2.1.0-3 -> 2.1.1-1)
[2013-09-19 20:46] [PACMAN] starting full system upgrade
[2013-09-19 20:48] [PACMAN] Running 'pacman -Rns psd'
[2013-09-19 20:48] [PACMAN] Running 'pacman -Rns profile-sync-daemon'
[2013-09-19 20:48] [PACMAN] removed profile-sync-daemon (5.40.1-1)
[2013-09-19 20:48] [PACMAN] removed rsync (3.0.9-6)
[2013-09-19 20:49] [PACMAN] Running 'pacman -Rns chromium'
[2013-09-19 20:49] [PACMAN] Running 'pacman -Syu'
[2013-09-19 20:49] [PACMAN] synchronizing package lists
[2013-09-19 20:49] [PACMAN] starting full system upgrade
[2013-09-19 20:50] [PACMAN] upgraded chromium (29.0.1547.65-1 -> 29.0.1547.76-1)
[2013-09-19 20:50] [PACMAN] upgraded xvidcore (1.3.2-1 -> 1.3.2-2)
[2013-09-19 20:58] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-dsana/PKGDEST.ZDK/chromium-pepper-flash-stable-2:11.8.800.170-1-x86_64.pkg.tar.xz'
[2013-09-19 20:58] [PACMAN] upgraded chromium-pepper-flash-stable (2:11.8.800.97-1 -> 2:11.8.800.170-1)
EDIT: journalctl doesn't show me anything interesting, other than the fact that chromium complains when it realizes that its profile data has gone missing.
Last edited by dsana123 (2013-09-21 16:02:48)

I think I have found the problem.
There was a gnome update earlier in the week. gnome-settings-daemon runs an hourly housekeeping job. I had set the "Automatically Purge Temporary Files" in the Privacy tab when setting up my laptop last month.
gnome-settings-daemon has decided to delete files in the /tmp directory (I can trigger this by clicking "Purge Temporary files" which then deletes my files in the /tmp directory). This does not happen in the previous gnome-settings-daemon. Anyway, I'll mark the thread SOLVED if my file in the /tmp directory survives the hour!
[2013-09-17 19:35] [PACMAN] upgraded gnome-desktop (1:3.8.3-2 -> 1:3.8.4-1)
[2013-09-17 19:35] [PACMAN] upgraded gnome-color-manager (3.8.2-1 -> 3.8.3-1)
[2013-09-17 19:35] [PACMAN] upgraded gnome-settings-daemon (3.8.4-2 -> 3.8.5-1)
[2013-09-17 19:35] [PACMAN] upgraded gnome-control-center (3.8.4.1-2 -> 3.8.5-1)
[2013-09-17 19:35] [PACMAN] upgraded gnome-themes-standard (3.8.3-1 -> 3.8.4-1)

Upgrade - Transport Directory Strategy

Hello All,
We are having the below 4.7 Landscape,
DEV -> QAS -> PRD
We are having central Transport Directory. /usr/sap/trans is present in PRD which is mounted to DEV and QAS.
Now, we are doing DEV Upgrade.
So, we have created a Temporary Development DVP for 4.7 (which is a copy of DEV) so that we can continue our 4.7 Developments. Basically a approach of Dual Landscapes for Upgrades, one for 4.7 and one for ECC6.
Now, DEV has its local /usr/sap/trans, while we have mounted /usr/sap/trans(of PRD) to DVP. So new 4.7 Landscape is
DVP-> QAS -> PRD
After I do my QAS Upgrade, 4.7 Landscape will be turned to a 2 System landscape. Because of H/W constraints we cannot have two QAS (one for 4.7 and other for ECC6).
My question is,
After I do my QAS Upgrade, should my QAS DIR_TRANS point to /usr/sap/trans of DEV or PRD?
I am planning to point it to that of DEV, we will have dual Central Trans Directories,
one for 4.7 Landscape (/usr/sap/trans in PRD) for DVP-> PRD
and the other for ECC 6 (/usr/sap/trans in DEV) for DEV -> QAS
What do I do after PRD upgrade? should my DIR_TRANS for ECC 6 PRD point to /usr/sap/trans of DEV ?
Thanks!

if you are upgrading in a parallel landscape , you really dont need to worry about the transport directory of the 4.7 landscape.
as soon as you upgrade the DEV , i guess you can have a DIR_TRANS pointing locally
and you can make that the Central transport directory for the ECC landscape
As i said earlier , you need to keep track of changes that are performed in the 4.7 landspace after the DEV upgrade and make sure they are recreated(if necessary) in the ECC landspace as part of the Dual maintanence.
As long as you keeo track of the changes that are happening in the 4.7 landspace and manage it approriately , you are fine.
Planning would be crucial.
Gerard

Change STMS transport directory

Hi gurus,
I have a High Availability SAP ERP system (SAP ECC 6.0) as PRD server. We used an old server for DEV system (Host name = sapdev). These two servers belonged to a STMS domain.
Recently we made homogeneous system copy and created a new Development (PRD copy) system to a new server. the new servers host name is AthinaDEV. We created a new STMS domain, joining the new DEV and PRD systems. The problem is that transport directory in PRD seams to be
sapdev\sapmnt\trans\ and in DEV seams to be
athinadev\sapmnt\trans\. In both servers in Transport Tool I have configured TRANSDIR as
athinadev\sapmnt\trans.
How can I change the transport directory to PRD to look
athinadev?
Thanks in advanced

OK,
I added the profile parameter DIR_TRANS with the correct path to both systems and now both systems use
athinadev\sapmnt\trans as transport domain. All seems to be correct now (all checks return success) but I can't transfer any request.
For example: I have created a test ABAP program. I have created a request for that program. I released the request from SE11 transaction succesffully. But when I use STMS transaction I have the following situation: in import overview I can see both systmes and 1 request waiting. When I double click on PRD to enter to import queue the list is empty.
I have cheked the permissions on trans folder and seems to be ok (prdadm has corrrect permissions).
The two systems has connected with transport routes.
Can anyone help me find the solution?

Unable to use global transport directory

Hi,
I have a 3 system SAP landscape consisting of DEV, QAS, PRD. I configured TMS and put all three system into the same transport group. DEV and QAS can shared the same transport directory residing in DEV. However I am unable to get PRD to use the global transport directory. PRD is always using its transport directory. How can I allow PRD to use the global transport directory?
Rdgs

Hi,
The transport directory is shared out which explains why QAS is able to use the same transport directory. DIR_TRANS in PRD points to local transport directory and not the shared transport directory. Is there really a need to set DIR_TRANS parameter if TMS is configured? In QAS, I don't see DIR_TRANS being set in the instance profile.
I did tried setting DIR_TRANS in PRD however the system reported the parameter as unknown.
BTW, PRD is a copied from another system. We migrated the old PRD to a new server.
Rdgs

UNIX permissions to NFS transport directory

I have upgraded lately to ERP 6.0 on HPUX /Oracle 10.
I have installed a NFS directory /usr/sap/trans .
When I release a transport request the owner is unknown (110) and the group (109).
The Productive system can see the file but has no access to it.
If I change the owner (chown) everything works fine.
What I have to do fix it ?
It sounds to me , there is a UNIX file that allows to insert shared users.
Thank you.

Hi,
the SIDadm user of DEV need to be domain user where you can provide him necessary access on the usr/sap/trans and same should be with Production, if the user was local only to DEV/PRD system then the DEV/PRD system trans directory cannot recognize and validate the permissions of SIDadm user.
You have to mount the usr/sap/trans of PRD onto usr/sap/trans of DEV so that what ever releases happens they will come and sits PRD trans directory and can be accessed by PRD.
Even when you mount the transport directory of PRD onto DEV, you should include the DEV system as trusted in PRD and viceversa.
Then this should work.
Regards...........
Edited by: Sita Rr Uppalapati on Jan 13, 2009 1:06 PM

How to share Common transport directory with Production

Dear All,
we are following three-system landscape with Dev & Qas on the same server & production server in a Cluster.Now I am going to start the production server installation but I have few query before starting the installation:
1. The Dev+Qas server is sharing a common transport directory (/usr/sap/trans). The production server needs to share the same transport directory.I have few options:
a)Should I need to share the common transport directory during the installation
b)I install the production server first then I can share the transport directory which is currently being shared by Dev & Qas system
c)I need to share the Common transport directory first & then start the installation so that during installation Production system writes into the Common traansport directory
Please advise.
Thanks in advance,
Sandipan

Hi,
By mounting, do you mean just to share it as we are using Windows Server 2003 x64 bit system, so just by sharing will it work.
Need your suggestion on whether can I install the production system first & then by sharing the transport directory from Dev( or Qas) it can join in the exisitng transport directory. As during installation of production server also,the system will create /usr/sap/trans. If I don't share the already exisitng /usr/sap/trans of Dev system, can I share it later so that production system can join into the common transport directory without any problem.
Please guide,
Thansk & Regards,
Sandipan

[svn] 3347: -remove the javascript directory since it is getting cleaned and recreated during the build process .

Revision: 3347
Author: [email protected]
Date: 2008-09-25 06:27:28 -0700 (Thu, 25 Sep 2008)
Log Message:
-remove the javascript directory since it is getting cleaned and recreated during the build process.
-this should make SVN happy and get the builds working again
Removed Paths:
flex/sdk/trunk/frameworks/javascript/FABridge/samples/srcview/source/fabridge/javascript/

- Where? That depends upon what you what. But, going by the letter of what you asked, you shouldn't deploy any applications or packages if you want them on your newly images systems, you should make them a part of the TS using Install Software and Install
Application tasks.
- How many times? You should only need one although depending upon what you are deploying and if you are using offline updates, some folks add more. I typically use two one right after the Setup Windows and ConfigMgr task (just like the task sequence wizard
builds for you) to update the OS and "things" in the image and one at the end to catch additional updates for apps and components added during the TS. Note that you also have to initiate an update scan cycle for additional install update tasks to work. Do
this by adding a run-command line task before the second Install Updates task with the proper WMIC incantation.
- Offline Updates only injects CBS updates into the image which are typically just core OS updates. You should also update your image though to include non-CBS updates. Using a build and catpure task sequence makes this easy.
Jason | http://blog.configmgrftw.com

Transport Directory and queue are out of sync after the restore

Hi all
I got a DEV server. Running ECC6 on MAXDB over linux. One user deleted some tables and we restored the database. No file system is restored.
Now we are having issues with the transports as the tranport directory is the latest and database is having old data about 3 days old data.
I am not able to see the same objects that we released in the old transports before the restore neither I am able to re-import the transport.
Please let me know the best way to make this in sync with the file system transports available.
Thanks
Shafquat

Thanks for the response. I think I am not clear in my problem statement.
We restored the whole database. Nothing at the fie system level is restored. So Trans directory is having up to date work done (Released transports etc) but after the restore the information coming through the database is the old information. Like in SE10 the transport that was released earlier still showing released but showing less number of objects than the one we actually released before the restore. Even if we try to re-import the same transport it ends up in the error.
Please let me know how we can make file system and database in sync.
Thanks again for the response.
Shafquat

Function Module not being displayed in the Transport Request

Hi,
I Created a FM "RH_ACTIVATE_WFOBJECT_AFTER_IMP" in my SAP System. After I created due to problem in editing I have deleted the FM and also deleted it from the request.
I have re created the function module and if I see the object directory entry I find the following
Identical request locks
Request User Task/request Object
**** ***** R3TR FUGR RHWS
In the request I cannot find the function module but only the function group. Please help me to get my function module visible in the transport request.

Hi ,
When your creating the FM for first timw with new FGRP then no need to worry .
You can see only the FGRP in the transport request number and when you move this transport request to further systems your FM automatically transport with the FGRP.
Next time when your creating a new FM under the FGRP which is already moved to production you can see only your FM name under the transport request.
When you go to FGRP main program by follwing the path
FGRP -> Disply FGRP in SE37 you can see the main program of the FGRP there if you see one include with TOP and XX .
double click on the XX Include.
there you can see allthe FM under that FGRP.
Thanks
Naresh

Cleaning Up the Transport Directory

Similar Messages

Maybe you are looking for