SAP BASIS ERROR during unicode conversion:error during conversion of cluster item

(DB) INFO: REGUC created #20120710113304

myCluster (55.23.Imp): 1596: inconsistent field count detected.

myCluster (55.23.Imp): 1599: nametab says field count (TDESCR) is 179.

myCluster (55.23.Imp): 1602: alternate nametab says field count (TDESCR) is 181.

myCluster (55.23.Imp): 1270: unable to retrieve nametab info for logic table REGUP     .

myCluster (55.23.Imp): 8166: unable to retrieve nametab info for logic table REGUP     .

myCluster (55.23.Imp): 2687: failed to convert cluster data of cluster item.

myCluster: REGUC      **700****20060206****00001O**** ****1000****0000310014****          ****                ****0100000002**

myCluster (55.23.Imp): 324: error during conversion of cluster item.

myCluster (55.23.Imp): 327: affected physical table is REGUC.

(CNV) ERROR: data conversion failed.  rc = 2

(DB) INFO: disconnected from DB

/sapmnt/PRD/exe/R3load: job finished with 1 error(s)

/sapmnt/PRD/exe/R3load: END OF LOG: 20120710113310

Solution : 

1. Incorrect data should be removed from source system before export of ABAP Database System.

2. At target System stop the current database import phase and perform under 

/tmp/sapinst_instdir/ECC50/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB

and 

•  Modify DDL<dbs>.TPL (<dbs> = ADA, DB2, DB4, DB6, IND, MSS, ORA) before the R3load TSK files are generated; search for the keyword "negdat:" and add "REGUC" and "VER_CLUSTR" to this line.

•  Modify the TSK file (most probably SAPCLUST.TSK) before the R3load import is (re-)started; search for the lines starting with "D REGUC I" and "D VER_CLUSTR I" and change the status (i.e. "err" or "xeq") to "ign" or remove the lines.

Also Refer SAP Note Number : 967124

3. Restart the database import phase .

CJS-00030 SAP Installation error.

First you will have to reset your installation and delete installation log directory.

1- Be sure that on the root session you are using to launch sapinst for DBInstance there is no ORACLE_HOME environment variable set.

2- Check your oraInst.loc file (see SAP note 350251), adapt it so that

inventory_loc=/oracle/oraInventory

and create directory if necessary. This avoid problems on unix with previous installations of oracle.

 ######################################################

Also

ORACLE_HOME=/opt/oracle/product/102_32 is not a valid path. 
it should be like 
/oracle/[SID]/102_32

#################################################################

Also comment out environment variable under file 

vim /root/.bash_profile

#ORACLE_HOME=/oracle/SID/102_32

ORA-00904 error Solution at the time of SAP Installation

ORA-00904: "SYS"."DBMS_EXPORT_EXTENSION"."FUNC_INDEX_DEFAULT": invalid identifier

[Problem]

Export: Release 9.2.0.8.0 - Production on Wed Jul 25 10:47:29 2007

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to: Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses UTF8 character set (possible charset conversion)

About to export specified tables via Direct Path ...
Current user changed to DBAPL
. . exporting table RPT_LOCAL__01 1012208 rows exported
EXP-00056: ORACLE error 904 encountered
ORA-00904: "SYS"."DBMS_EXPORT_EXTENSION"."FUNC_INDEX_DEFAULT": invalid identifier
Export terminated successfully with warnings.

[Root Cause]

It caused by different DB version in the server , as below two version is installed:

DB1 V9.2.0.8 , while DB2 is 9.2.0.5

In operator id 's env , the ORACLE_HOME is point to 9.2.0.8, caused using higher version exp to exp data from lower version db.

[solution]
in the script , explicitly specify the path of exp , i.e:

/software/oradb1/product/9.2.0/bin/exp $RPT_CONNECT@$RPT_DB file=$expfile log=$LOGFILE direct=y recordlength=65535 buffer=10240000 compress=N tables=${tab_name} statistics=none

Today 21-Jan-2009, hit another similar case. get new findings from metalink

Doc ID:

358508.1

.

Applies to:

Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 10.2.0.1
This problem can occur on any platform.

Symptoms

Export fails with:

EXP-00056: ORACLE error 904 encountered
ORA-00904: "SYS"."DBMS_EXPORT_EXTENSION"."FUNC_INDEX_DEFAULT": invalid identifier

Changes

A patchset was recently installed against the database.

Cause

After the patchset installation, the data dictionary components have not been upgraded to the patchset release (e.g. 10.1.0.4)

A patchset (e.g. 10.1.0.4) was applied to an existing ORACLE_HOME install but one or more of the patchset steps were not performed per the patchset readme to bring the database components up to the same version as the patched software as shown in DBA_REGISTRY.

If the database components versions do not match the software and the running instance, then the exp utility fails as it finds an earlier version of the exp packages in the database.

Solution

Follow the Post-Installation Tasks section of the Oracle Database Server Patch Set Notes to run the catpatch.sql script with the database started in migrate mode and then retry the export.

Connect to the database as SYSDBA and run:

SQL> STARTUP MIGRATE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catpatch.sql
SQL> SPOOL OFF
SQL> SHUTDOWN
SQL> STARTUP

Step By Step Update SAP Kernel in UNIX based

1. Login as root

2. Make new backup directory
cd /
mkdir 09062010                         (Date based)

3. Create latest kernel backup
cp -pr /sapmnt/SID/exe/* /09062010

4. Compare the original kernel and the backup
du -sk /sapmnt/SID/exe/  840413 /sapmnt/SID/exe #
du -sk /SIDkernel_10102007  841992 /SIDkernel_10102007 #

5. Make new shadow kernel directory
cd /
mkdir kernel

6. Copy the new downloaded kernel files into /kernel

7. Unpack the new downloaded kernel in folder /kernel
SAPCAR -xvf SAPEXE_175-20000221.SAR     
SAPCAR -xvf SAPEXEDB_175-20000223.SAR

8. Login as sidadm

9. Stop the SAP System
stopsap

10. Stop saposcol
saposcol -k

11. Login as root

12. Go to the current kernel directory
cd /usr/sap/SID/SYS/exe/run

13. Copy all extracted support packages into this folder
cp -pr /kernel/* /usr/sap/SID/SYS/exe/run

14. Copy back the original file saproot.sh into this folder.
cp -p /09062010/saproot.sh  /usr/sap/SID/SYS/exe/run

15. Go to the current kernel directory
cd /sapmnt/SID/exe
Then run:
./saproot.sh SID

16. Login as sidadm

17. Start the saposcol service
saposcol

18. Start the SAP system
startsap

NOTE:  Download the latest patch level from https://websmp109.sap-ag.de/support path Support Packages and Patches - Entry by Application Group Additional Components SAP Kernel SAP KERNEL 32-BIT UNICODE SAP KERNEL 6.40 32-BIT UNICODE

Download only two .SAR files e.g

SAPEXE_175-20000221.SAR     
SAPEXEDB_175-20000223.SAR

#Database independent

#Oracle

Rebuilding of Index in SAP

1      In transaction SE14, enter the name of your table and select Edit
2) On the resulting screen, select Indexes.
3) Select the Index you wish to rebuild
4) Select the appropriate Execute Database Operation
5) Go back (using the green arrow) to the Table definition
Repeat steps 2 --> 5 till all indexes have been rebuilt

2     Check statistics in transaction DB20

VB Script to convert Excel sheet into .csv format

Open Notepad, create a file called XlsToCsv.vbs and paste this in:

if WScript.Arguments.Count < 2 Then

    WScript.Echo "Error! Please specify the source path and the destination. Usage: XlsToCsv SourcePath.xls Destination.csv"

    Wscript.Quit

End If

Dim oExcel

Set oExcel = CreateObject("Excel.Application")

Dim oBook

Set oBook = oExcel.Workbooks.Open(Wscript.Arguments.Item(0))

oBook.SaveAs WScript.Arguments.Item(1), 6

oBook.Close False

oExcel.Quit

WScript.Echo "Done"

Then from a command line, go to the folder you saved the .vbs file in and run:

XlsToCsv.vbs [sourcexlsFile].xls [destinationcsvfile].csv

This requires Excel to be installed on the machine you are on though.

VMware Tools for Linux Guests

On a Linux guest, you can install VMware Tools within X or from the command line

·  Installing VMware Tools within X

·  Installing VMware Tools from the Command Line with the Tar Installer

·  Installing VMware Tools from the Command Line with the RPM Installer

Installing VMware Tools within X

You can install VMware Tools within X using the .tar installer in a terminal window. See Installing VMware Tools from the Command Line with the Tar Installer.

To install VMware Tools from X with the RPM installer:

1. Choose VM > Install VMware Tools.

The guest operating system mounts the VMware Tools installation virtual CD.

2. Double-click the VMware Tools CD icon on the desktop.

Note: In some Linux distributions, the VMware Tools CD icon may fail to appear when you install VMware Tools within an X windows session on a guest. In this case, you should continue installing VMware Tools as described in Installing VMware Tools from the Command Line with the Tar Installer, beginning with step 3.

3. Double-click the RPM installer in the root of the CD-ROM.

4. Enter the root password.

5. Click Continue.

The installer prepares the packages.

6. Click Continue when the installer presents a dialog box saying Completed System Preparation.

A dialog appears for Updating system, with a progress bar. When the installer is done, VMware Tools are installed. There is no confirmation or finish button.

7. In an X terminal, as root (su -), configure VMware Tools.

vmware-config-tools.pl

Respond to the questions the installer displays on the screen. Press Enter to accept the default value.

Note: Be sure to respond yes when the installer offers to run the configuration program.

8. Launch the VMware Tools background application:

vmware-toolbox &

Note: Some guest operating systems require a reboot for full functionality.

Installing VMware Tools from the Command Line with the Tar Installer

The first steps are performed on the host, within Workstation menus:

1. Power on the virtual machine.

2. After the guest operating system has started, prepare your virtual machine to install VMware Tools.

Choose VM > Install VMware Tools.

The remaining steps take place inside the virtual machine.

3. As root (su -), mount the VMware Tools virtual CD-ROM image, change to a working directory (for example, /tmp), uncompress the installer, then unmount the CD-ROM image.

Note: Some Linux distributions automatically mount CD-ROMs. If your distribution uses automounting, do not use the mount and umount commands below. You still must untar the VMware Tools installer to /tmp.

Some Linux distributions use different device names or organize the /dev directory differently. If your CD-ROM drive is not /dev/cdrom or if the mount point for a CD-ROM is not /mnt/cdrom, you must modify the following commands to reflect the conventions used by your distribution.

mount /dev/cdrom /mnt/cdrom

cd /tmp

Note: If you have a previous installation, delete the previous vmware-distrib directory before installing. The default location of this directory is
/tmp/vmware-tools-distrib.

4. Untar the VMware Tools tar file:

tar zxf /mnt/cdrom/VMwareTools-5.0.0-<xxxx>.tar.gz

umount /dev/cdrom

Where <xxxx> is the build/revision number of the VMware Workstation release.

Note: If you attempt to install a tar installation over an rpm installation — or the reverse — the installer detects the previous installation and must convert the installer database format before continuing.

5. Run the .tar VMware Tools installer:

cd vmware-tools-distrib

./vmware-install.pl

Respond to the configuration questions on the screen. Press Enter to accept the default value.

6. Log off of the root account.

exit

7. Start X and your graphical environment.

8. In an X terminal, launch the VMware Tools background application.

vmware-toolbox &

Note: You may run VMware Tools as root or as a normal user. To shrink virtual disks, you must run VMware Tools as root (su -).

Installing VMware Tools from the Command Line with the RPM Installer

The first steps are performed on the host, within Workstation menus:

1. Power on the virtual machine.

2. After the guest operating system has started, prepare your virtual machine to install VMware Tools.

Choose VM > Install VMware Tools.

The remaining steps take place inside the virtual machine.

3. As root (su -), mount the VMware Tools virtual CD-ROM image, change to a working directory (for example, /tmp), uncompress the installer, then unmount the CD-ROM image.

Note: Some Linux distributions automatically mount CD-ROMs. If your distribution uses automounting, do not use the mount and umount commands below. You still must untar the VMware Tools installer to /tmp.

Some Linux distributions use different device names or organize the /dev directory differently. If your CD-ROM drive is not /dev/cdrom or if the mount point for a CD-ROM is not /mnt/cdrom, you must modify the following commands to reflect the conventions used by your distribution.

mount /dev/cdrom /mnt/cdrom

cd /tmp

Note: If you have a previous installation, delete the previous vmware-distrib directory before installing. The default location of this directory is
/tmp/vmware-tools-distrib.

4. At the command prompt, enter:

rpm -Uhv /mnt/cdrom/VMwareTools-5.0.0-<xxxx>.i386.rpm

umount /dev/cdrom

Where <xxxx> is the build/revision number of the VMware Workstation release.

Note: If you attempt to install an rpm installation over a tar installation — or the reverse — the installer detects the previous installation and must convert the installer database format before continuing.

5. Configure VMware Tools:

vmware-config-tools.pl

Respond to the questions the installer displays on the screen. Press Enter to accept the default value.

6. Log off of the root account.

exit

7. Start X and your graphical environment.

8. In an X terminal, launch the VMware Tools background application.

vmware-toolbox &

Note: You may run VMware Tools as root or as a normal user. To shrink virtual disks, you must run VMware Tools as root (su -).

Starting VMware Tools Automatically

You may find it helpful to configure your guest operating system so VMware Tools starts when you start your X server. The steps for doing so vary depending on your Linux distribution and your desktop environment. Check your operating system documentation for the appropriate steps to take.

For example, in a Red Hat Linux 7.1 guest using GNOME, follow these steps.

1. Open the Startup Programs panel in the GNOME Control Center.

Main Menu (click the foot icon in the lower left corner of the screen) > Programs > Settings > Session > Startup Programs

2. Click Add.

3. In the Startup Command field, enter vmware-toolbox.

4. Click OK, click OK again, then close the GNOME Control Center.

The next time you start X, VMware Tools starts automatically.

Uninstalling VMware Tools

To remove VMware Tools from your Linux guest operating system, log on as root (su -) and enter the following command:

·  From a tar install

vmware-uninstall-tools.pl

·  From an RPM install

rpm -e VMwareTools