Hello,

How can I create new data class (tabart) to assign it to a dedicated tablespace from TAORA table?

Thanks

Hi all,

I hope someone can help me.

We have a problem with the startup of our sap instances when the database is running on another node.

The problem is, that the startdb doesn't find the remote database and start the database local on the node.

I have a flexframe infrastructure and all sap instances are single services like db, scs, ci, app

The Flexframe starts the services step by step in the correct sequence.

In the first step flexframe starts the database on the remote host correctly and

in the next step flexframe starts the ci.

In the protocols I find the successfull checks with R3Trans and TNSPING.

In the step "sapcontrol starts the instance" is implemented a wait of 10 seconds.

During this windows the startdb-script is running.

The tnsnames adapter resolves the alias correct.

After that step the function "check_db_running"

is running and this function starts the database local.

At the moment we stop the unconnected database-instance and the system works without any problems.

Here the protocols:

The startsap.trc has following infos:

    }09:40:47 ## restore_path() done

    EXEDIR=/usr/sap/SID/DVEBMGS00/exe

    EXECMD=/usr/sap/SID/DVEBMGS00/exe/R3trans

   }09:40:47 ## getExePath() done: 0

   DBCONNECT_TEST=/usr/sap/SID/DVEBMGS00/exe/R3trans -d -w

...

   }09:40:48 ## restore_path() done

   Database is running

   DB_RUNNING=1

   JDB_RUNNING=

  }09:40:48 ## set_db_running() done: 1

  {09:40:48 ## set_sapjdbhost() start

....

   }09:41:02 ## sapstartsrv_do() done: 0

   starting SAP Instance DVEBMGS00

   Startup-Log is written to /home_sap/sidadm/startsap_DVEBMGS00.log

   /usr/sap/SID/DVEBMGS00/exe/sapcontrol -prot NI_HTTP -nr 00 -function Start

   wait sleep 10 while instance is starting

   Instance on host hostname started

  }09:41:14 ## instance_do() done

_______________________________

STARTDB.LOG

------------------------------ Thu Oct 23 09:41:03 CEST 2014

checking V2 connect

TNS Ping Utility for Linux: Version 11.2.0.3.0 - Production on 23-OCT-2014 09:41:03

Copyright (c) 1997, 2011, Oracle.  All rights reserved.

Used parameter files:

/sapmnt/SID/profile/oracle/sqlnet.ora

Used TNSNAMES adapter to resolve the alias

Attempting to contact (DESCRIPTION = (ADDRESS = (COMMUNITY = SAP.WORLD)(PROTOCOL = TCP)(HOST = xxxx)(PORT = x

)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = SID)))

OK (0 msec)

tnsping: V2 connect to SID

------------------------------ Thu Oct 23 09:41:03 CEST 2014

Connect to the database to check the database state:

-------------------------------------------------------------

Thu Oct 23 09:41:03 CEST 2014

check if Oracle processes are running

database not available

There are no Oracle processes running -

Database is probably already stopped.

check_db_running: check finished with return code: 10

Database not available

____________

Has anybody an idea where is my problem?

Best regards

Peter

Hi Friends,

We are running SAP BIW 7.10 on Linux and Oracle 11g.

We are facing issue in ODS jobs many times the ODS jobs got hanged  and it doesn't completed. After that we manually terminate the jobs and start it again. We have 4 DB nodes in oracle RAC and 8 SAP application instances.

We have checked the trace log and found many times the alert as "IPC Send timeout detected. Sender: ospid 8949 [oracle@<DB hosts>"

Regards

Ganesh Tiwari

Hi,

due a OS/DB Migration to ASE/Windows we need to upgrade our ECC landscape to ECC 6.05 (6.0 EHP5) that is the minimum release for Sybase ASE.

Now the system is on Solaris 10 SPARC, Oracle 10.2.0.4 Unicode... so, can I upgrade from 6.00 to 6.05 without Oracle upgrade? ... I wouldn't upgrade to Oracle 11.2... but if it is mandatory I will be adapting to it.

Thank you.

Dear Experts.

I am trying to extend the tablespace but getting error, i have tried digging into the issue and checked the permissions and updated the brtools with latest available still the same error. The issue is arising after system refresh. Please find the screenshot attached.

Experts please help me to resolve the issue.

Thanks & Regards

Mohd

Hi Guys,

would like to know email id for SAP Manager who sits in Oracle Corporation for SAP Production.

Pls. post the requested instruction for me.

Thanks in Advance,

Sivakumar KS.

SAP System refresh with offline drive back up

Hi,

I wanted to perform quality system refresh.Client had provided offline backup of drives.Prodcuion system SID is P11 and Quality system SID is QI1.

Data file are for  Production system  are as below.

SQL> select name from v$datafile;

NAME

--------------------------------------------------------------------------------

R:\ORACLE\P11\SAPDATA1\SYSTEM_1\SYSTEM.DATA1

R:\ORACLE\P11\SAPDATA1\UNDO_1\UNDO.DATA1

R:\ORACLE\P11\SAPDATA1\SYSAUX_1\SYSAUX.DATA1

R:\ORACLE\P11\SAPDATA3\SR3_1\SR3.DATA1

R:\ORACLE\P11\SAPDATA3\SR3_2\SR3.DATA2

R:\ORACLE\P11\SAPDATA3\SR3_3\SR3.DATA3

R:\ORACLE\P11\SAPDATA3\SR3_4\SR3.DATA4

R:\ORACLE\P11\SAPDATA3\SR3_5\SR3.DATA5

R:\ORACLE\P11\SAPDATA3\SR3_6\SR3.DATA6

R:\ORACLE\P11\SAPDATA3\SR3_7\SR3.DATA7

R:\ORACLE\P11\SAPDATA3\SR3_8\SR3.DATA8

NAME

--------------------------------------------------------------------------------

R:\ORACLE\P11\SAPDATA3\SR3_9\SR3.DATA9

R:\ORACLE\P11\SAPDATA3\SR3_10\SR3.DATA10

R:\ORACLE\P11\SAPDATA3\SR3_11\SR3.DATA11

R:\ORACLE\P11\SAPDATA3\SR3_12\SR3.DATA12

R:\ORACLE\P11\SAPDATA3\SR3_13\SR3.DATA13

R:\ORACLE\P11\SAPDATA3\SR3_14\SR3.DATA14

R:\ORACLE\P11\SAPDATA3\SR3_15\SR3.DATA15

R:\ORACLE\P11\SAPDATA3\SR3_16\SR3.DATA16

S:\ORACLE\P11\SAPDATA2\SR3701_1\SR3701.DATA1

S:\ORACLE\P11\SAPDATA2\SR3701_2\SR3701.DATA2

S:\ORACLE\P11\SAPDATA2\SR3701_3\SR3701.DATA3

NAME

--------------------------------------------------------------------------------

S:\ORACLE\P11\SAPDATA2\SR3701_4\SR3701.DATA4

S:\ORACLE\P11\SAPDATA2\SR3701_5\SR3701.DATA5

S:\ORACLE\P11\SAPDATA2\SR3701_6\SR3701.DATA6

S:\ORACLE\P11\SAPDATA2\SR3701_7\SR3701.DATA7

S:\ORACLE\P11\SAPDATA2\SR3701_8\SR3701.DATA8

S:\ORACLE\P11\SAPDATA2\SR3701_9\SR3701.DATA9

S:\ORACLE\P11\SAPDATA2\SR3701_10\SR3701.DATA10

S:\ORACLE\P11\SAPDATA2\SR3701_11\SR3701.DATA11

S:\ORACLE\P11\SAPDATA2\SR3701_12\SR3701.DATA12

S:\ORACLE\P11\SAPDATA2\SR3701_13\SR3701.DATA13

S:\ORACLE\P11\SAPDATA2\SR3701_14\SR3701.DATA14

NAME

--------------------------------------------------------------------------------

S:\ORACLE\P11\SAPDATA2\SR3701_15\SR3701.DATA15

S:\ORACLE\P11\SAPDATA2\SR3701_16\SR3701.DATA16

S:\ORACLE\P11\SAPDATA2\SR3701_17\SR3701.DATA17

S:\ORACLE\P11\SAPDATA2\SR3701_18\SR3701.DATA18

S:\ORACLE\P11\SAPDATA2\SR3701_19\SR3701.DATA19

S:\ORACLE\P11\SAPDATA2\SR3701_20\SR3701.DATA20

S:\ORACLE\P11\SAPDATA4\SR3USR_1\SR3USR.DATA1

R:\ORACLE\P11\SAPDATA3\SR3_17\SR3.DATA17

S:\ORACLE\P11\SAPDATA2\SR3701_21\SR3701.DATA21

S:\ORACLE\P11\SAPDATA2\SR3701_22\SR3701.DATA22

S:\ORACLE\P11\SAPDATA2\SR3701_23\SR3701.DATA23

NAME

--------------------------------------------------------------------------------

R:\ORACLE\P11\SAPDATA1\SYSAUX_2\SYSAUX.DATA2

R:\ORACLE\P11\SAPDATA3\SR3_18\SR3.DATA18

R:\ORACLE\P11\SAPDATA3\SR3_19\SR3.DATA19

S:\ORACLE\P11\SAPDATA2\SR3701_24\SR3701.DATA24

R:\ORACLE\P11\SAPDATA3\SR3_20\SR3.DATA20

R:\ORACLE\P11\SAPDATA3\SR3_21\SR3.DATA21

R:\ORACLE\P11\SAPDATA3\SR3_22\SR3.DATA22

S:\ORACLE\P11\SAPDATA4\SR3USR_2\SR3USR.DATA2

R:\ORACLE\P11\SAPDATA3\SR3_23\SR3.DATA23

R:\ORACLE\P11\SAPDATA3\SR3_24\SR3.DATA24

S:\ORACLE\P11\SAPDATA4\SR3USR_3\SR3USR.DATA3

NAME

--------------------------------------------------------------------------------

R:\ORACLE\P11\SAPDATA3\SR3_25\SR3.DATA25

R:\ORACLE\P11\SAPDATA3\SR3_26\SR3.DATA26

R:\ORACLE\P11\SAPDATA3\SR3_27\SR3.DATA27

R:\ORACLE\P11\SAPDATA3\SR3_28\SR3.DATA28

R:\ORACLE\P11\SAPDATA3\SR3_29\SR3.DATA29

R:\ORACLE\P11\SAPDATA3\SR3_30\SR3.DATA30

R:\ORACLE\P11\SAPDATA3\SR3_31\SR3.DATA31

R:\ORACLE\P11\SAPDATA3\SR3_32\SR3.DATA32

R:\ORACLE\P11\SAPDATA3\SR3_33\SR3.DATA33

R:\ORACLE\P11\SAPDATA3\SR3_34\SR3.DATA34

R:\ORACLE\P11\SAPDATA3\SR3_35\SR3.DATA35

NAME

--------------------------------------------------------------------------------

R:\ORACLE\P11\SAPDATA3\SR3_36\SR3.DATA36

R:\ORACLE\P11\SAPDATA3\SR3_37\SR3.DATA37

S:\ORACLE\P11\SAPDATA4\SR3USR_4\SR3USR.DATA4

S:\ORACLE\P11\SAPDATA4\SR3USR_5\SR3USR.DATA5

S:\ORACLE\P11\SAPDATA4\SR3USR_6\SR3USR.DATA6

S:\ORACLE\P11\SAPDATA4\SR3USR_7\SR3USR.DATA7

S:\ORACLE\P11\SAPDATA4\SR3USR_8\SR3USR.DATA8

S:\ORACLE\P11\SAPDATA4\SR3USR_9\SR3USR.DATA9

S:\ORACLE\P11\SAPDATA4\SR3USR_10\SR3USR.DATA10

S:\ORACLE\P11\SAPDATA4\SR3USR_11\SR3USR.DATA11

S:\ORACLE\P11\SAPDATA4\SR3USR_12\SR3USR.DATA12

NAME

--------------------------------------------------------------------------------

S:\ORACLE\P11\SAPDATA4\SR3USR_13\SR3USR.DATA13

S:\ORACLE\P11\SAPDATA4\SR3USR_14\SR3USR.DATA14

S:\ORACLE\P11\SAPDATA4\SR3USR_15\SR3USR.DATA15

S:\ORACLE\P11\SAPDATA4\SR3USR_16\SR3USR.DATA16

S:\ORACLE\P11\SAPDATA4\SR3USR_17\SR3USR.DATA17

S:\ORACLE\P11\SAPDATA4\SR3USR_18\SR3USR.DATA18

S:\ORACLE\P11\SAPDATA4\SR3USR_19\SR3USR.DATA19

S:\ORACLE\P11\SAPDATA4\SR3USR_20\SR3USR.DATA20

S:\ORACLE\P11\SAPDATA4\SR3USR_21\SR3USR.DATA21

S:\ORACLE\P11\SAPDATA4\SR3USR_22\SR3USR.DATA22

S:\ORACLE\P11\SAPDATA4\SR3USR_23\SR3USR.DATA23

NAME

--------------------------------------------------------------------------------

S:\ORACLE\P11\SAPDATA4\SR3USR_24\SR3USR.DATA24

S:\ORACLE\P11\SAPDATA4\SR3USR_25\SR3USR.DATA25

S:\ORACLE\P11\SAPDATA4\SR3USR_26\SR3USR.DATA26

S:\ORACLE\P11\SAPDATA4\SR3USR_27\SR3USR.DATA27

92 rows selected.

Data file are for  Quality system  are as below.

SQL> select name from v$datafile;

NAME

--------------------------------------------------------------------------------

S:\ORACLE\QI1\SAPDATA1\SYSTEM_1\SYSTEM.DATA1

S:\ORACLE\QI1\SAPDATA1\UNDO_1\UNDO.DATA1

S:\ORACLE\QI1\SAPDATA1\SYSAUX_1\SYSAUX.DATA1

S:\ORACLE\QI1\SAPDATA3\SR3_1\SR3.DATA1

S:\ORACLE\QI1\SAPDATA3\SR3_2\SR3.DATA2

S:\ORACLE\QI1\SAPDATA3\SR3_3\SR3.DATA3

S:\ORACLE\QI1\SAPDATA3\SR3_4\SR3.DATA4

S:\ORACLE\QI1\SAPDATA3\SR3_5\SR3.DATA5

S:\ORACLE\QI1\SAPDATA3\SR3_6\SR3.DATA6

S:\ORACLE\QI1\SAPDATA3\SR3_7\SR3.DATA7

S:\ORACLE\QI1\SAPDATA3\SR3_8\SR3.DATA8

NAME

--------------------------------------------------------------------------------

S:\ORACLE\QI1\SAPDATA3\SR3_9\SR3.DATA9

S:\ORACLE\QI1\SAPDATA3\SR3_10\SR3.DATA10

S:\ORACLE\QI1\SAPDATA3\SR3_11\SR3.DATA11

S:\ORACLE\QI1\SAPDATA3\SR3_12\SR3.DATA12

S:\ORACLE\QI1\SAPDATA3\SR3_13\SR3.DATA13

S:\ORACLE\QI1\SAPDATA3\SR3_14\SR3.DATA14

S:\ORACLE\QI1\SAPDATA3\SR3_15\SR3.DATA15

S:\ORACLE\QI1\SAPDATA3\SR3_16\SR3.DATA16

R:\ORACLE\QI1\SAPDATA2\SR3701_1\SR3701.DATA1

R:\ORACLE\QI1\SAPDATA2\SR3701_2\SR3701.DATA2

R:\ORACLE\QI1\SAPDATA2\SR3701_3\SR3701.DATA3

NAME

--------------------------------------------------------------------------------

R:\ORACLE\QI1\SAPDATA2\SR3701_4\SR3701.DATA4

R:\ORACLE\QI1\SAPDATA2\SR3701_5\SR3701.DATA5

R:\ORACLE\QI1\SAPDATA2\SR3701_6\SR3701.DATA6

R:\ORACLE\QI1\SAPDATA2\SR3701_7\SR3701.DATA7

R:\ORACLE\QI1\SAPDATA2\SR3701_8\SR3701.DATA8

R:\ORACLE\QI1\SAPDATA2\SR3701_9\SR3701.DATA9

R:\ORACLE\QI1\SAPDATA2\SR3701_10\SR3701.DATA10

R:\ORACLE\QI1\SAPDATA2\SR3701_11\SR3701.DATA11

R:\ORACLE\QI1\SAPDATA2\SR3701_12\SR3701.DATA12

R:\ORACLE\QI1\SAPDATA2\SR3701_13\SR3701.DATA13

R:\ORACLE\QI1\SAPDATA2\SR3701_14\SR3701.DATA14

NAME

--------------------------------------------------------------------------------

R:\ORACLE\QI1\SAPDATA2\SR3701_15\SR3701.DATA15

R:\ORACLE\QI1\SAPDATA2\SR3701_16\SR3701.DATA16

R:\ORACLE\QI1\SAPDATA2\SR3701_17\SR3701.DATA17

R:\ORACLE\QI1\SAPDATA2\SR3701_18\SR3701.DATA18

R:\ORACLE\QI1\SAPDATA2\SR3701_19\SR3701.DATA19

R:\ORACLE\QI1\SAPDATA2\SR3701_20\SR3701.DATA20

S:\ORACLE\QI1\SAPDATA4\SR3USR_1\SR3USR.DATA1

S:\ORACLE\QI1\SAPDATA3\SR3_17\SR3.DATA17

R:\ORACLE\QI1\SAPDATA2\SR3701_21\SR3701.DATA21

R:\ORACLE\QI1\SAPDATA2\SR3701_22\SR3701.DATA22

R:\ORACLE\QI1\SAPDATA2\SR3701_23\SR3701.DATA23

NAME

--------------------------------------------------------------------------------

S:\ORACLE\QI1\SAPDATA1\SYSAUX_2\SYSAUX.DATA2

S:\ORACLE\QI1\SAPDATA3\SR3_18\SR3.DATA18

S:\ORACLE\QI1\SAPDATA3\SR3_19\SR3.DATA19

R:\ORACLE\QI1\SAPDATA2\SR3701_24\SR3701.DATA24

S:\ORACLE\QI1\SAPDATA3\SR3_20\SR3.DATA20

S:\ORACLE\QI1\SAPDATA3\SR3_21\SR3.DATA21

S:\ORACLE\QI1\SAPDATA3\SR3_22\SR3.DATA22

S:\ORACLE\QI1\SAPDATA4\SR3USR_2\SR3USR.DATA2

S:\ORACLE\QI1\SAPDATA3\SR3_23\SR3.DATA23

S:\ORACLE\QI1\SAPDATA3\SR3_24\SR3.DATA24

S:\ORACLE\QI1\SAPDATA4\SR3USR_3\SR3USR.DATA3

NAME

--------------------------------------------------------------------------------

S:\ORACLE\QI1\SAPDATA3\SR3_25\SR3.DATA25

S:\ORACLE\QI1\SAPDATA3\SR3_26\SR3.DATA26

S:\ORACLE\QI1\SAPDATA3\SR3_27\SR3.DATA27

S:\ORACLE\QI1\SAPDATA3\SR3_28\SR3.DATA28

S:\ORACLE\QI1\SAPDATA3\SR3_29\SR3.DATA29

S:\ORACLE\QI1\SAPDATA3\SR3_30\SR3.DATA30

S:\ORACLE\QI1\SAPDATA3\SR3_31\SR3.DATA31

S:\ORACLE\QI1\SAPDATA3\SR3_32\SR3.DATA32

S:\ORACLE\QI1\SAPDATA3\SR3_33\SR3.DATA33

S:\ORACLE\QI1\SAPDATA3\SR3_34\SR3.DATA34

S:\ORACLE\QI1\SAPDATA3\SR3_35\SR3.DATA35

NAME

--------------------------------------------------------------------------------

S:\ORACLE\QI1\SAPDATA3\SR3_36\SR3.DATA36

S:\ORACLE\QI1\SAPDATA3\SR3_37\SR3.DATA37

S:\ORACLE\QI1\SAPDATA4\SR3USR_4\SR3USR.DATA4

S:\ORACLE\QI1\SAPDATA4\SR3USR_5\SR3USR.DATA5

S:\ORACLE\QI1\SAPDATA4\SR3USR_6\SR3USR.DATA6

S:\ORACLE\QI1\SAPDATA4\SR3USR_7\SR3USR.DATA7

S:\ORACLE\QI1\SAPDATA4\SR3USR_8\SR3USR.DATA8

S:\ORACLE\QI1\SAPDATA4\SR3USR_9\SR3USR.DATA9

S:\ORACLE\QI1\SAPDATA4\SR3USR_10\SR3USR.DATA10

S:\ORACLE\QI1\SAPDATA4\SR3USR_11\SR3USR.DATA11

S:\ORACLE\QI1\SAPDATA4\SR3USR_12\SR3USR.DATA12

NAME

--------------------------------------------------------------------------------

S:\ORACLE\QI1\SAPDATA4\SR3USR_13\SR3USR.DATA13

S:\ORACLE\QI1\SAPDATA4\SR3USR_14\SR3USR.DATA14

S:\ORACLE\QI1\SAPDATA4\SR3USR_15\SR3USR.DATA15

S:\ORACLE\QI1\SAPDATA4\SR3USR_16\SR3USR.DATA16

S:\ORACLE\QI1\SAPDATA4\SR3USR_17\SR3USR.DATA17

S:\ORACLE\QI1\SAPDATA4\SR3USR_18\SR3USR.DATA18

S:\ORACLE\QI1\SAPDATA4\SR3USR_19\SR3USR.DATA19

S:\ORACLE\QI1\SAPDATA4\SR3USR_20\SR3USR.DATA20

S:\ORACLE\QI1\SAPDATA4\SR3USR_21\SR3USR.DATA21

S:\ORACLE\QI1\SAPDATA4\SR3USR_22\SR3USR.DATA22

S:\ORACLE\QI1\SAPDATA4\SR3USR_23\SR3USR.DATA23

NAME

--------------------------------------------------------------------------------

S:\ORACLE\QI1\SAPDATA4\SR3USR_24\SR3USR.DATA24

S:\ORACLE\QI1\SAPDATA4\SR3USR_25\SR3USR.DATA25

S:\ORACLE\QI1\SAPDATA4\SR3USR_26\SR3USR.DATA26

91 rows selected.

Can I copy datafile from source to destionation?

e.g

R:\ORACLE\P11\SAPDATA1\SYSTEM_1\SYSTEM.DATA1 to

S:\ORACLE\QI1\SAPDATA1\SYSTEM_1\SYSTEM.DATA1

Same way all datafiles and logfiles as source to destination.

Does it works after creating control file from PRD system? Still now I had restore using brtools only.

Please suggest me does it work? and also send me System refresh Pre and Post activity.

Regards,

Sahil K

Team,

I want to drop the unused tablespace including data files in Oracle 10.2.

Our previous version of SAP & DB is SAP R/3 4.6C & Oracle  and upgraded to ERP 6.0 EHP4 & Oracle 10.2.0.2(last 2 yrs back)

There was one old unused tablespace in my Database, it occupied the free space 40 GB. I want to drop this tablespace.

Table space Name : PSAPSID46C

Anybody Please find the attached screenhot for reference.

I checked couple of times, drop that table space after that the oracle was down. I can't up the database.

Give the correct solution. Plse help me.

Thank You,

Regards,

A.Sithanandan

Hi SDNners,

We've just completed a system copy of our SolMan 3.1 system onto a new

(Xeon x64 based) server. This system copy is part of the process of

moving SolMan 3.1 from an old server onto 64bit hardware and then

upgrading it to SolMan v4 and Oracle 10G.

Although the system appears to start properly in the MMC, we are unable

to log into the system through SAPGUI - we get a SYNTAX_ERROR window

instead of a logon screen.

I've checked the SysLog from within the MMC and noticed a number of

errors stating:

Database: Table VSEOPARENT is not in the database

Database: Table VSEOIFIMPL is not in the database

Database: Table VSEOIFCOMP is not in the database

I tried running SQL command 'select * from "SAPSOL"."VSEOPARENT"; and

it confirmed that the table didn't exist. I then ran the same command

on the source SolMan system and it showed that VSEOPARENT DID exist. I

don't understand how these VSEO* tables could have gone missing between

the source and target systems.

I've searched OSS for VSEO* and cannot find anything. Please help!

Thanks,

Arwel.

Hi all

We are running several vehicle searches in transaction VELO with TREX enabled. In most cases, TREX seems to correctly operate and the search is quicker than with TREX disabled, as expected.

However, in one scenario, the search with TREX enabled is significantly slower.

The criteria for this search is:

Velo Filter: Vehicle Status

Availability Data: IV

Production Date: 06.01.2014 (from and to)

We have traced the search and have seen the following SQL running:

SELECT

  "MANDT", "VGUID", "VHCLE", "MATNR", "LIFNR", "CHARG", "EQUNR", "WERKS", "LGORT", "BWTAR",

  "CUOBJ", "CUABA", "MMCTR", "MMSTA", "MMTSP", "SDCTR", "SDSTA", "SDTSP", "KUNNR", "ENDCU",

  "VHVIN", "VHCEX", "AVAIL", "VBLTY", "LOCTN", "GPRICE", "GPRICECUKY", "CDTSP", "PSTSP", "PDTSP",

  "ERNAM", "VHUSG", "CMPGN", "PCOUNT", "PCOUNT_U", "IMMATDATE", "VHSAR", "VHORD", "SHLVL",

  "ARCHIVE_FLAG", "USED_VEHICLE"

FROM

  "VLCVEHICLE"

WHERE

  "MANDT"=:A0 AND "PDTSP" BETWEEN :A1 AND :A2 AND "VGUID" IN (:A3 ,:A4 ,:A5 ,:A6 ,:A7 ) AND "MATNR"

  IN (:A8 ,:A9 ,:A10 ,:A11 ,:A12 ,:A13 ,:A14 ,:A15 ,:A16 ,:A17 ,:A18 ,:A19 ,:A20 ,:A21 ,:A22 ,:A23

  ,:A24 ,:A25 ,:A26 ,:A27 ,:A28 ,:A29 ,:A30 ,:A31 ,:A32 ,:A33 ,:A34 ,:A35 ,:A36 ,:A37 ,:A38 ,:A39

  ,:A40 ,:A41 ,:A42 ,:A43 ,:A44 ,:A45 ,:A46 ,:A47 ,:A48 ,:A49 ,:A50 ,:A51 ,:A52 ,:A53 ,:A54 ,:A55

  ,:A56 ,:A57 ,:A58 ,:A59 ,:A60 ,:A61 ,:A62 ,:A63 ,:A64 ,:A65 ,:A66 ,:A67 ,:A68 ,:A69 ,:A70 ,:A71

  ,:A72 ,:A73 ,:A74 ,:A75 ,:A76 ,:A77 ,:A78 ,:A79 ,:A80 ,:A81 ,:A82 ,:A83 ,:A84 ,:A85 ,:A86 ,:A87

  ,:A88 ,:A89 ,:A90 ,:A91 ,:A92 ,:A93 ,:A94 ,:A95 ,:A96 ,:A97 ,:A98 ,:A99 ,:A100 ,:A101 ,:A102

  ,:A103 ,:A104 ,:A105 ,:A106 ,:A107 ,:A108 ,:A109 ,:A110 ,:A111 ,:A112 ,:A113 ,:A114 ,:A115 ,:A116

  ,:A117 ,:A118 ,:A119 ,:A120 ,:A121 ,:A122 ,:A123 ,:A124 ,:A125 ,:A126 ,:A127 ,:A128 ,:A129 ,:A130

  ,:A131 ,:A132 ,:A133 ,:A134 ,:A135 ,:A136 ,:A137 ,:A138 ,:A139 ,:A140 ,:A141 ,:A142 ,:A143 ,:A144

  ,:A145 ,:A146 ,:A147 ,:A148 ,:A149 ,:A150 ,:A151 ,:A152 ,:A153 ,:A154 ,:A155 ,:A156 ,:A157 ,:A158

  ,:A159 ,:A160 ,:A161 ,:A162 ,:A163 ,:A164 ,:A165 ,:A166 ,:A167 ,:A168 ,:A169 ,:A170 ,:A171 ,:A172

  ,:A173 ,:A174 ,:A175 ,:A176 ,:A177 ,:A178 ,:A179 ,:A180 ,:A181 ,:A182 ,:A183 ,:A184 ,:A185 ,:A186

  ,:A187 ,:A188 ,:A189 ,:A190 ,:A191 ,:A192 ,:A193 ,:A194 ,:A195 ,:A196 ,:A197 ,:A198 ,:A199 ,:A200

  ,:A201 ,:A202 ,:A203 ,:A204 ,:A205 ,:A206 ,:A207 ,:A208 ,:A209 ,:A210 ,:A211 ,:A212 ,:A213 ,:A214

  ,:A215 ,:A216 ,:A217 ,:A218 ,:A219 ,:A220 ,:A221 ,:A222 ,:A223 ,:A224 ,:A225 ,:A226 ,:A227 ,:A228

  ,:A229 ,:A230 ,:A231 ,:A232 ,:A233 ,:A234 ,:A235 ,:A236 ,:A237 ,:A238 ,:A239 ,:A240 ,:A241 ,:A242

  ,:A243 ,:A244 ,:A245 ,:A246 ,:A247 ,:A248 ,:A249 ,:A250 ,:A251 ,:A252 ,:A253 ,:A254 ,:A255 ,:A256

  ,:A257 ,:A258 ,:A259 ,:A260 ,:A261 ,:A262 ,:A263 ,:A264 ,:A265 ,:A266 ,:A267 ,:A268 ,:A269 ,:A270

  ,:A271 ,:A272 ,:A273 ,:A274 ,:A275 ,:A276 ,:A277 ,:A278 ,:A279 ,:A280 ,:A281 ,:A282 ,:A283 ,:A284

  ,:A285 ,:A286 ,:A287 ,:A288 ,:A289 ,:A290 ,:A291 ,:A292 ,:A293 ,:A294 ,:A295 ,:A296 ,:A297 ,:A298

  ,:A299 ,:A300 ,:A301 ,:A302 ,:A303 ,:A304 ,:A305 ,:A306 ,:A307 ,:A308 ,:A309 ,:A310 ,:A311 ,:A312

  ,:A313 ,:A314 ,:A315 ,:A316 ,:A317 ,:A318 ,:A319 ,:A320 ,:A321 ,:A322 ,:A323 ,:A324 ,:A325 ,:A326

  ,:A327 ,:A328 ,:A329 ,:A330 ,:A331 ,:A332 ,:A333 ,:A334 ,:A335 ,:A336 ,:A337 ,:A338 ,:A339 ,:A340

  ,:A341 ,:A342 ,:A343 ,:A344 ,:A345 ,:A346 ,:A347 ,:A348 ,:A349 ,:A350 ,:A351 ,:A352 ,:A353 ,:A354

  ,:A355 ,:A356 ,:A357 ,:A358 ,:A359 ,:A360 ,:A361 ,:A362 ,:A363 ,:A364 ,:A365 ,:A366 ,:A367 ,:A368

  ,:A369 ,:A370 ,:A371 ,:A372 ,:A373 ,:A374 ,:A375 ,:A376 ,:A377 ,:A378 ,:A379 ,:A380 ,:A381 ,:A382

  ,:A383 ,:A384 ,:A385 ,:A386 ,:A387 ,:A388 ,:A389 ,:A390 ,:A391 ,:A392 ,:A393 ,:A394 ,:A395 ,:A396

  ,:A397 ,:A398 ,:A399 ,:A400 ,:A401 ,:A402 ,:A403 ,:A404 ,:A405 ,:A406 ,:A407 )

The ABAP trace shows 'Select VLCVEHICLE' as taking 369 seconds from a gross time of 444 seconds. This is an exceptionally long time for a query that would appear to be efficient (at least, according to the SQL execution plan) - it is searching on VGUID which it has obtained via TREX (but why does it still query PDTSP? Surely if TREX has returned the relevant VGUIDs then it doesn't need this - could this be the cause of the performance  issue?).

With TREX disabled, the SQL captured is like so:

SELECT "MANDT", "VGUID", "VHCLE", "MATNR", "LIFNR", "CHARG", "EQUNR", "WERKS", "LGORT", "BWTAR", "CUOBJ",

"CUABA", "MMCTR", "MMSTA", "MMTSP", "SDCTR", "SDSTA", "SDTSP", "KUNNR", "ENDCU", "VHVIN", "VHCEX", "AVAIL",

"VBLTY", "LOCTN", "GPRICE", "GPRICECUKY", "CDTSP", "PSTSP", "PDTSP", "ERNAM", "VHUSG", "CMPGN", "PCOUNT",

"PCOUNT_U", "IMMATDATE", "VHSAR", "VHORD", "SHLVL", "ARCHIVE_FLAG", "USED_VEHICLE" FROM "VLCVEHICLE" WHERE

"MANDT"=:A0 AND "AVAIL"=:A1 AND "PDTSP" BETWEEN :A2 AND :A3 AND "MATNR" IN (:A4 ,:A5 ,:A6 ,:A7 ,:A8 ,:A9 ,:A10

,:A11 ,:A12 ,:A13 ,:A14 ,:A15 ,:A16 ,:A17 ,:A18 ,:A19 ,:A20 ,:A21 ,:A22 ,:A23 ,:A24 ,:A25 ,:A26 ,:A27 ,:A28

,:A29 ,:A30 ,:A31 ,:A32 ,:A33 ,:A34 ,:A35 ,:A36 ,:A37 ,:A38 ,:A39 ,:A40 ,:A41 ,:A42 ,:A43 ,:A44 ,:A45 ,:A46

,:A47 ,:A48 ,:A49 ,:A50 ,:A51 ,:A52 ,:A53 ,:A54 ,:A55 ,:A56 ,:A57 ,:A58 ,:A59 ,:A60 ,:A61 ,:A62 ,:A63 ,:A64

,:A65 ,:A66 ,:A67 ,:A68 ,:A69 ,:A70 ,:A71 ,:A72 ,:A73 ,:A74 ,:A75 ,:A76 ,:A77 ,:A78 ,:A79 ,:A80 ,:A81 ,:A82

,:A83 ,:A84 ,:A85 ,:A86 ,:A87 ,:A88 ,:A89 ,:A90 ,:A91 ,:A92 ,:A93 ,:A94 ,:A95 ,:A96 ,:A97 ,:A98 ,:A99 ,:A100

,:A101 ,:A102 ,:A103 ,:A104 ,:A105 ,:A106 ,:A107 ,:A108 ,:A109 ,:A110 ,:A111 ,:A112 ,:A113 ,:A114 ,:A115 ,:A116

,:A117 ,:A118 ,:A119 ,:A120 ,:A121 ,:A122 ,:A123 ,:A124 ,:A125 ,:A126 ,:A127 ,:A128 ,:A129 ,:A130 ,:A131 ,:A132

,:A133 ,:A134 ,:A135 ,:A136 ,:A137 ,:A138 ,:A139 ,:A140 ,:A141 ,:A142 ,:A143 ,:A144 ,:A145 ,:A146 ,:A147 ,:A148

,:A149 ,:A150 ,:A151 ,:A152 ,:A153 ,:A154 ,:A155 ,:A156 ,:A157 ,:A158 ,:A159 ,:A160 ,:A161 ,:A162 ,:A163 ,:A164

,:A165 ,:A166 ,:A167 ,:A168 ,:A169 ,:A170 ,:A171 ,:A172 ,:A173 ,:A174 ,:A175 ,:A176 ,:A177 ,:A178 ,:A179 ,:A180

,:A181 ,:A182 ,:A183 ,:A184 ,:A185 ,:A186 ,:A187 ,:A188 ,:A189 ,:A190 ,:A191 ,:A192 ,:A193 ,:A194 ,:A195 ,:A196

,:A197 ,:A198 ,:A199 ,:A200 ,:A201 ,:A202 ,:A203 ,:A204 ,:A205 ,:A206 ,:A207 ,:A208 ,:A209 ,:A210 ,:A211 ,:A212

,:A213 ,:A214 ,:A215 ,:A216 ,:A217 ,:A218 ,:A219 ,:A220 ,:A221 ,:A222 ,:A223 ,:A224 ,:A225 ,:A226 ,:A227 ,:A228

,:A229 ,:A230 ,:A231 ,:A232 ,:A233 ,:A234 ,:A235 ,:A236 ,:A237 ,:A238 ,:A239 ,:A240 ,:A241 ,:A242 ,:A243 ,:A244

,:A245 ,:A246 ,:A247 ,:A248 ,:A249 ,:A250 ,:A251 ,:A252 ,:A253 ,:A254 ,:A255 ,:A256 ,:A257 ,:A258 ,:A259 ,:A260

,:A261 ,:A262 ,:A263 ,:A264 ,:A265 ,:A266 ,:A267 ,:A268 ,:A269 ,:A270 ,:A271 ,:A272 ,:A273 ,:A274 ,:A275 ,:A276

,:A277 ,:A278 ,:A279 ,:A280 ,:A281 ,:A282 ,:A283 ,:A284 ,:A285 ,:A286 ,:A287 ,:A288 ,:A289 ,:A290 ,:A291 ,:A292

,:A293 ,:A294 ,:A295 ,:A296 ,:A297 ,:A298 ,:A299 ,:A300 ,:A301 ,:A302 ,:A303 ,:A304 ,:A305 ,:A306 ,:A307 ,:A308

,:A309 ,:A310 ,:A311 ,:A312 ,:A313 ,:A314 ,:A315 ,:A316 ,:A317 ,:A318 ,:A319 ,:A320 ,:A321 ,:A322 ,:A323 ,:A324

,:A325 ,:A326 ,:A327 ,:A328 ,:A329 ,:A330 ,:A331 ,:A332 ,:A333 ,:A334 ,:A335 ,:A336 ,:A337 ,:A338 ,:A339 ,:A340

,:A341 ,:A342 ,:A343 ,:A344 ,:A345 ,:A346 ,:A347 ,:A348 ,:A349 ,:A350 ,:A351 ,:A352 ,:A353 ,:A354 ,:A355 ,:A356

,:A357 ,:A358 ,:A359 ,:A360 ,:A361 ,:A362 ,:A363 ,:A364 ,:A365 ,:A366 ,:A367 ,:A368 ,:A369 ,:A370 ,:A371 ,:A372

,:A373 ,:A374 ,:A375 ,:A376 ,:A377 ,:A378 ,:A379 ,:A380 ,:A381 ,:A382 ,:A383 ,:A384 ,:A385 ,:A386 ,:A387 ,:A388

,:A389 ,:A390 ,:A391 ,:A392 ,:A393 ,:A394 ,:A395 ,:A396 ,:A397 ,:A398 ,:A399 ,:A400

The SQL looks less efficient, as would be expected without TREX, but this is only taking 53 seconds to run whereas with TREX enabled it is taking over 7 minutes!

Please can you explain why this is?

The execution plan for the first query shows an estimated cost of only 2; the second shows around 5000 - however, I realised that you can't directly compare costs for different statements. But can anyone else see why the first query would take so much longer?

Thanks

Ross

Hello Experts,

I am trying query a column values from a cube using DB02 SQL Editor. I am able to get data using standard table like RSDDIME ect. When I try to use underlying table from a given cube, it bombs. Here is what I tried:

Ex: select 0FISCPER from "/BIC/EZMM_C01". I tried prefixing the system ID and didn't work.

Getting ORA-00903 or 942  > Table doesn't exist or invalid table name.

Please shed some light.

Thanks

Ravi

Hello Oracle-experts,

we are trying to integrate sap systems running with Oracle database centrally into Solution Manager (also running with Oracle database).

By doing so we get the error ORA-12638. We read that it should be possible to set SQLNET.AUTHENTIFICATION_SERVICES from NTS to NONE in order to avoid this error.

Unfortunately after this the ops$-user cannot be used.

Is there some workaround on the one hand to integrate sap systems running with Oracle database centrally into DBACOCKPIT into Solution manager and on the other hand still to use ops$-user?

Thank you! 

kind regards

hello everyone,

fora solutioninmy companyI want to use"SmartData Access" as thereplicationtoolofOracleDBtables inSAPHANADB.I havereadthat "Smart DataAccess forHANA"supportstheOracle 12c version.However,I am usingOracle11g version,cansomeoneplease confirmthat "Smart Data Access" also supports the OracleDB 11g version.

Thank you

Hello,

How can I create new data class (tabart) to assign it to a dedicated tablespace from TAORA table?

Thanks

Hi Experts,

                  How can we find the tables size in sap? is there any Transaction code is available?

I want to see the all tables and their size in Tablespace PSAP<SID>.

How i can do it?

Kindly help me

Regards,

Sundar.C

Hi all,

Am mainly an Oracle DBA and had just recently return to supporting SAP customers after a 4 year absence of supporting non-SAP customers.




Anyway, I have some question on using Oracle RMAN with SAP databases. Backup softwares are Netbackup and Data Protector.




I managed to get the backup working, that is, there is no issues, Oracle RMAN backup using SAP's brarchive and brbackup works alright. My question is about using an Oracle RMAN catalog. I've read thru several SAP documentation and cannot find one where I can use a RMAN catalog.




Reading from




http://help.sap.com/saphelp_nw04/helpdata/en/d1/43d7cab9a04a409cc46876e36762c2/content.htm

Does that mean I cannot use a RMAN catalog? Had anyone managed to use a RMAN catalog to do the RMAN backup?

*Another question I have is, do I need Netbackup and Data Protector if I want to run RMAN backup to disk via brarchive and brbackup? Does backint requires a SBT library to use RMAN? What I mean is, I want to use RMAN but doing backup to disk instead of to tape which means I don't need the tape library installed, will backint know that this is the case and will not look for the tape library?




Any advise or feedback on this will be very much appreciated. Thanks in advance.




Extracts from http://help.sap.com/saphelp_nw04/helpdata/en/d1/43d7cab9a04a409cc46876e36762c2/content.htm are as below:




The Oracle Recovery Manager (RMAN) is an Oracle backup program. You can use it as a command line interface (CLI) or as a graphical user interface (GUI) in the Oracle Enterprise Manager (OEM). We support RMAN with the SAP backup tools BRBACKUP and BRARCHIVE.




RMAN uses the System Backup to Tape (SBT) interface to back up to tape devices. We implement SBT using the SAP backup library. External backup tools can implement this interface as a dynamic link library (DLL).
Integration




By integrating RMAN into BRBACKUP, you can add security and flexibility to important functions in existing backup strategies and tools:




· The recovery catalog is not used. The backup information is stored in the control file. After the backup, the control file is also backed up. In a restore, the control file is restored first, followed by the data files.




· The integration of RMAN into BRBACKUP also guarantees integration into the SAP Structure linkComputing Center Management System (CCMS).




· BRBACKUP tape management functions as previously (that is, as when using the SAP backup library).




· You can still use the BACKINT interface with external tools.




· All previous SAP backup strategies are supported while using RMAN. Nevertheless, RMAN is not supported for standby database backups and split-mirror backups.




· The following components are delivered with the standard Oracle8 installation:




¡ RMAN with the Oracle SBT interface




¡ Backup library and backup tool Networker from Legato




¡ Legatou2019s BACKINT interface implementation (as of Oracle 8.0.5)




The SAP installation also delivers the SAP backup library with BRBACKUP and BRARCHIVE.

Edited by: newbie01.sap on Jun 11, 2010 10:50 AM

Hi Experts,

My production system Tablespace PSAPSR3 is 100% and it is autoextended on mode what it will leads to.!

[SEARCH FIRST. THREAD LOCKED. MODERATOR]

Hi,
We have installed fiori launch Pad. And Now unble to find out fiori Launch Pad version.

Can anyone help?

we have gateway system

SAP_BASIS 731 0009

SAP_ABA 731 0009

PI_BASIS 731 0009

ST-PI 2008_1_710 0009

GW_CORE 200 0008

SAP_BW 731 0009

UI2_700 100 0008

UI2_701 100 0008

UI2_702 100 0008

UI2_731 100 0008

UI2_FND 100 0008

UI2_SRVC 100 0008

UI5_731 100 0008

UISAPUI5 100 0008

UI_INFRA 100 0008

IW_FND 250 0008

IW_PGW 100 0004

WEBCUIF 731 0008

IW_BEP 200 0008

IW_CBS 200 0008

IW_CNT 200 0008

UIX01HCM 100 0003

UIX01SRM 100 0002

Hi,

In the standby server logs are not applying & it ends with following error message

-------------

SQL*Plus: Release 10.2.0.4.0 - Production on Fri Oct 17 07:00:31 2014

Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.

SQL> SQL> Connected.

SQL>

SQL> SQL> ORA-00279: change 4567483678 generated at 10/15/2014 18:07:53 needed for thread 1

ORA-00289: suggestion : /oracle/PRD/oraarch/standby/PRDarch1_57308_696018700.dbfORA-00280: change 4567483678 for thread 1 is in sequence #57308

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

ORA-00310: archived log contains sequence 57305; sequence 57308 required

ORA-00334: archived log: '/oracle/PRD/oraarch/standby/PRDarch1_57305_696018700.dbf'

SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.

--------------

In the archive log folder all the log files are available. From 57200 to 57320

Why this sort of error occurs and how to solve this. (missing the sequence,and it occurs quite regularly as well)

In above, why its ignore 57306, 57307 & asking for 57308

regards,

zerandib

Dear Experts,

I have upgraded the Oracle 10g to 11g after that Offline backup was failing,but online with redo-logs was successful.

Please suggest i have been trying to sort it out since 3 days.