Error with dbca -silent ASM storage type

dbca -silent -createDatabase -templateName General_Purpose.dbc \
-gdbName $LOWER_SID -sid $LOWER_SID \
-sysPassword P1casso -systemPassword P1casso \
-sysmanPassword P1casso -dbsnmpPassword P1casso -asmsnmpPassword P1casso \
-emConfiguration LOCAL \
-storageType ASM -diskGroupName DATA_DM01 \
-totalMemory 1024 -automaticMemoryManagement true \
-nodeinfo dm01db01,dm01db02 -characterset AL32UTF8 -nationalCharacterSet AL16UTF16 \
-obfuscatedPasswords false -sampleSchema true \
-oratabLocation /etc/oratab
I get the following error
Creating and starting Oracle instance
ORA-01503: CREATE CONTROLFILE failed
ORA-01565: error in identifying file '+DATA_DM01/test2/system01.dbf'
ORA-17503: ksfdopn:2 Failed to open file +DATA_DM01/test2/system01.dbf
ORA-15001: diskgroup "DATA_DM01" does not exist or is not mounted
ORA-15204: database version 11.2.0.0.0 is incompatible with diskgroup DATA_DM01
Please can I know what the problem or what parameter setting are missed

user5846399 wrote:
dbca -silent -createDatabase -templateName General_Purpose.dbc \
-gdbName $LOWER_SID -sid $LOWER_SID \
-sysPassword P1casso -systemPassword P1casso \
-sysmanPassword P1casso -dbsnmpPassword P1casso -asmsnmpPassword P1casso \
-emConfiguration LOCAL \
-storageType ASM -diskGroupName DATA_DM01 \
-totalMemory 1024 -automaticMemoryManagement true \
-nodeinfo dm01db01,dm01db02 -characterset AL32UTF8 -nationalCharacterSet AL16UTF16 \
-obfuscatedPasswords false -sampleSchema true \
-oratabLocation /etc/oratab
I get the following error
Creating and starting Oracle instance
ORA-01503: CREATE CONTROLFILE failed
ORA-01565: error in identifying file '+DATA_DM01/test2/system01.dbf'
ORA-17503: ksfdopn:2 Failed to open file +DATA_DM01/test2/system01.dbf
ORA-15001: diskgroup "DATA_DM01" does not exist or is not mounted
ORA-15204: database version 11.2.0.0.0 is incompatible with diskgroup DATA_DM01
Please can I know what the problem or what parameter setting are missedwhat about ur asm instance. Is it started??
$ export ORACLE_SID=+ASM1
$ sqlplus / as sysdba
SQL> select group_number, name, value from v$asm_attribute;
SQL> select name, COMPATIBILITY, DATABASE_COMPATIBILITY from v$asm_diskgroup;
if your compatible on diskgroups be "10.1" or "10.2", you can change to 11.2
SQL> alter diskgroup DATA set attribute 'compatible.asm'='11.2';
Hope this may help you
--neeraj

Similar Messages

10g: Clone database with DBCA silent option

Hello community,
I have tried now for several times to make a clone of my existing database with DBCA and "-silent" option. I could improve my progress in cloning but now I always stick in the following error:
But first, what I have done so far:
1. Created a clone template of my Database with command:
dbca -silent -createCloneTemplate -sourceSID DBORIGIN -templateName myTest.dbc -datafileJarLocation /tmp/oratest
2. Create the clone-database by using the template from (1.) with command:
dbca -silent -createDatabase -templateName myTest.dbc -cloneTemplate -gdbname DBCLONE -sid DBCLONE -datafileJarLocation /tmp/oratest -datafileDestination /oradata -responseFile NO_VALUE -characterset AL32UTF8
Then the progress of execution is shown, it ends with a link to a log file. In this log file I can see the following contents:
==============================
Copying database files
DBCA_PROGRESS : 1%
DBCA_PROGRESS : 3%
DBCA_PROGRESS : 11%
DBCA_PROGRESS : 18%
DBCA_PROGRESS : 26%
DBCA_PROGRESS : 33%
DBCA_PROGRESS : 37%
Creating and starting Oracle instance
ORA-01503: CREATE CONTROLFILE failed
ORA-00200: control file could not be created
ORA-00202: control file: '/oradata/DBCLONE/<OMF_CONTROL_0>'
ORA-27040: file create error, unable to create file
DBCA_PROGRESS : 38%
ORA-00210: cannot open the specified control file
ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 4168
ORA-06512: at line 1
ORA-01507: database not mounted
DBCA_PROGRESS : 40%
DBCA_PROGRESS : 41%
ORA-01503: CREATE CONTROLFILE failed
ORA-00200: control file could not be created
ORA-00202: control file: '/oradata/DBCLONE/<OMF_CONTROL_0>'
ORA-27040: file create error, unable to create file
ORA-01507: database not mounted
DBCA_PROGRESS : 46%
DBCA_PROGRESS : 47%
ORA-01219: database not open: queries allowed on fixed tables/views only
ORA-01507: database not mounted
DBCA_PROGRESS : 52%
ORA-01219: database not open: queries allowed on fixed tables/views only
ORA-01507: database not mounted
DBCA_PROGRESS : 53%
DBCA_PROGRESS : 58%
ORA-06550: line 1, column 7:
PLS-00201: identifier 'DBMS_DATAPUMP_UTL.REPLACE_DEFAULT_DIR' must be declared
and so on
=====================================================
I have no idea where the "<OMF_CONTROL_0>" comes from. It is nowhere included in my myTest.dbc-file. In my eyes, it looks like that DBCA tries to create the file exactly with this filename - and this fails on Solaris, sure...
Here is, what I have in my template file "myTest.dbc" regarding the control files:
=======================
<ControlfileAttributes id="Controlfile">
<maxDatafiles>100</maxDatafiles>
<maxLogfiles>16</maxLogfiles>
<maxLogMembers>3</maxLogMembers>
<maxLogHistory>1</maxLogHistory>
<maxInstances>8</maxInstances>
<image name="o1_mf_2k1zmdmp_.ctl" filepath="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/"/>
<image name="o1_mf_2k1zmdvo_.ctl" filepath="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/"/>
</ControlfileAttributes>
====================================
To be honest, it is the first time that i try to use the DBCA with all these "special" options, especially the silent mode.
Does anyone have an idea what is going wrong in my case described here? What do I or could I change to come to a success clone?
Maybe, you can tell me where I can find some kind of "how to" for creating a clone using the silent-option.
Thanks a lot in advance for helping a newbie! ;-)
Regards
FireFighter

Hello,
finally I was successful in installing the clone of my DB. :-)
You remember that I had problems with the control files and these looked very strange:
control_files=("/oradata/DBCLONE/<OMF_CONTROL_0>","/oradata/DBCLONE/<OMF_CONTROL_1>")
The hint to check the permission in "/oradata" was a good one. The permissions were right all the time, but Oracle's DBCA was not able to create the sub-directory "DBCLONE". When I created it manually before installing the clone, the installation worked fine!
I'm still wondering about this because all other subdirectories were created automatically during running "dbca" (e.g. all subdirectories "DBCLONE" needed below the $ORACLE_BASE/admin/-directory like adump,bdump and so on...).
And i'm wondering about the names of the control files:
I expected that these strange OMF-names would be replaced by a "normal" file name. But "dbca" was able to create the files exactly with the names "<OMF_CONTROL_0>" and "<OMF_CONTROL_0>"...
As I had understood so far from OMF-concept, isn't the idea that Oracle takes care of file-naming instead of myself? I mean it can't be that I have to enter the template for DBCA and manually enter the control files names...
I'm still close to the thought that it be a bug that isn't documented until now. Maybe, when I have some time left I will open a service request at metalink.
If you are interested in this I will keep you informed on this topic. The other way round I stay interested in your opions and hints for using "dbca" to make and install a DB-clone.
Thanks again for you effort to help me as a rookie in Oracle. :-)
Regards
FireFighter

9iR2 database generating error with DBCA

I am using WinXP Proffessional Edition and setting up Oracle 9iR2 Database Server Enterprise Edition with Software Only option(my previous trials always fail generating new database) When ever I am trying to generate a database with DBCA(Database Configuration Assistant), again it fails when "Creating and Starting Oracle instance", giving "CreateProcess: null -new -sid MYDB1 -startmode m error=2" and the error follows it "ora-12560: tns: protocol adapter error" and all operation fails...
listener.ora content:
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT =
1521)))
(ADDRESS_LIST =(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0)))
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = C:\oracle\ora92)
(PROGRAM = extproc)
sqlnet.ora content:
NAMES.PREFERRED_SERVERS =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
SQLNET.AUTHENTICATION_SERVICES= (NONE)
Oracle services running during database creation
-OracleMTSRecoveryService
-OracleOraHome92Agent
-OracleOraHome92HTTPServer
-OracleOraHome92TNSListener
Hey people, what would the solution be, how would I generate database without getting headache?

Try this - create the new database with the name/SID of orcl and give it a try...

Installing Oracle 10g R2 (10.2) on Windows Error with DBCA

Hello, 10g R2 for Windows was released yesterday. I am trying to install it on a Windows 2000 computer. I choose an advanced install, general purpose database. The software installs fine, and then it gets to the wizards at the end.
The first wizard is the Oracle Net Configuration Assistant. That works fine.
Then it goes to DBCA. This gets an error right away. No DBCA windows pop up or anything. I don't see any error messages in the log files. If I cancel and double click dbca.bat in the <ORACLE_HOME>/bin/ directory nothing happens. If I try to run dbca.bat from a DOS prompt it says:
c:\oracle\10.2\mydatabase\bin> dbca.bat
The input line is too long.
The syntax of the command is incorrect.
I'm really lost. I don't know how to fix this problem. Has anyone else had trouble? Any ideas?
thank you!
~ T r o y ~

Actually, to overcome this problem I ran DBCA from the Windows start menu and this worked fine. Odd that it gave an error after the software installation and using dbca.bat.
Though, the DBCA shortcut in the Start menu points to:
<ORACLE_HOME>\product\10.2.0\db_1\BIN\launch.exe <ORACLE_HOME>\Oracle\product\10.2.0\db_1\assistants\dbca dbca.cl

SUT Error at TO Creation from Non-SU to SU managed Storage type

Hi
I am creating TO to move quants from Non-SU Manged Storage type to SU managed Storage type, but at first its giving error saying Enter SUT for storage type. These Non-SU managed Storage types are not having SUT Check but SU Managed storage type is having SUT Check.
I tried to update WM view-2 with SUT and palletization but still issue exists.
I am having batch job for RLAUTA10 where TR is converted to TO but due to above issue , this batch job is getting failed.
I am deseperately trying to find the root cause and fix this asap. Let me know how this issue can be resolved??
Thanks

Like I mentioned earlier in my posts, SU's are typically not managed in interim storage types. Apparently, in this case, the PSA is an SU managed location and you are trying to move inventory from a non-SU ST to SU PSA ST. The isse that you are encountering is due to the reason that the palletization data maintained in the material master is defaulted during receipts rather than staging therefore, the SUT field in the TR remains blank. But, due to business reasons you are using SU's in PSA's then you'd have to venture into development options to include SU types during automatic converion of staging TRs into TOs.

Delivery creation with respect to Storage Type

Hi Gurus,
Can we have a control on the deliveries creation with respect to the storage Types.
The situation is to have the outbound deliveries created only from a perticular storage type neglecting other storage types. Is there any customization?
Thanks
Shashidhar

Hi ,
For this you have to define storage type serch strategy,
Path,
LE> WM>Master data >Material>storage type indicator \
LE> WM>Master data >Material>storage section indicator
Then,
LE> WM>Strategires>activate storage type serch (whmaintion indicator -- st type)
LE> WM>Strategires-->activate storage section serch (wh -- maintion indicator -- st section)
Maintain the material master with warehouse number & storage type.
( In the case of fixed bin maintain the storage bin in wm-2 view)
Maintain the storage type indicator & storage section indicator.
If you have allready maintained the storage type search strategy then remove the symbol *** from yor storage type search.
Dev

Stock in storage type 999

Hi,
       Actually when we confirm a picking stock transfer order, if it has diferences, stock goes automatically to 999 storage type.
We have the problem that ATP (sales availability) looks at plant level, so if the stock in 999 is unrestric, sales orders confirm that stock (if no stock in other storage type).
So, we have to block or to put in quality control.
There is an standar procedure that when we confirm diferences in the picking stock transfer, stock goes automatically to 999 storage type, but like block stock? It means, that sap change the status automatically of the stock that goes to 999 storage type?
Thanks in advance for the help.
Regards
Enzo

Hello,
During sales order creation, avaibility check carried out at IM level. Hence even though you block the quant at storage type level, stock would be available for sales. I would suggest following
( 1) configure posting change LQ02- of WM-IM by going in to following path
       OLML--->WM>Interface>Inventory management-->Define posting change -
>define movement type
      configure unrestricted to block and block to unrestricted movement type for your warehouse.
(2) Schedule background job of LQ02 transaction code -- Program RLLQ0200 with variant as 999 storage type, your warehouse number and WM movement type of unrestricted to block. Schedule the job at regular interval.
The result of this schedule is, stock would be blocked in IM as well as WH level and will not be available for sales.
Thanks,
Milind

Error during Goods Issue using movement type U61

Dear All,
There is this error with respect to goods movement type U61. It states u201C Difference in Object List header data: U61 previously /321 Newu201D
I get this error when I am doing the Goods issue using the transaction EM10 or MB1A
Any guidance or help is welcome
Regards
Balaji.J

Hi,
The goods issue movement type is 501, the previous movement type was also 501 only. The status of the device is in ESTO. By doing goods issue using movemenn type U61, I need to make them in to AVLB status.
Regards
Balaji.J

Search for material from 2 Storage types

Hi,
When creating a delivery for Subcon PO Via ME2O the transfer order is created automatically from the source storage type
657 ( for example). The requirement is that the system should also look for material from source storage type 460 ( for example).
I did the following customization ( SPRO path):
1) Logistics execution -> Warehouse management -> Strategies -> Activate storage type search - > Determine search sequence --
For the combination of Warehouse number & Mvt type 541 ( GI to Subcon delivery) -- 657 and 460 are assigned.
2) Logistics execution -> Warehouse management -> Activities-> Transfers-> Define Mvt types-> For the combination of Warehouse number & Mvt type 541 -- I have assigned source storage type as 657.
With the above the system does the search from 657 stoarge type only and not from the both.
Is there any other setting to meet this requiremnet?
Best regards,
Prasad

Hi,
I removed 657 source storage type in the 541 mvt type set up ( Source storage type is Blank) . In the Movement Type set up for 541, "Ref.Stor.Type.Search" field is already with 541.
The Storage Type search sequence is maintained for the combination warehouse number & 541 mvt as 657 and 460 ( storage types).
When Delivery is created for Subcon PO, The Transfer order is not created automatcially ( Only delivery is created)
The requirement in detail is as below:
There are 2 plants ( AL70 & AL77) linked to 1 Warehouse (AL1). When delivery is created for subcon PO in plant AL70, the TO is also created automatically with source storage type as 657 and destination storage type as 916. The additional requirement is when delivery is created for Subcon PO in plant AL77, the TO aslo should be created automatically with source storage type as 460 and destination storage type as 916.
Regards,
Prasad

Restore Database to non-ASM Storage - Issue with Bigfile Tablespace

I have been testing a restore of my prod database that uses ASM (and oracle managed files) for storage to a different server and non-ASM storage. Oracle version is 10g EE. My database has one bigfile tablespace and it's datafile is about 250GB. The restore fails and it has something to do with the bigfile tablespace.
Here is the rman restore script:
run
set newname for datafile 1 to '/ora01/db/ehr/system01.dbf';
set newname for datafile 2 to '/ora01/db/ehr/undotbs01.dbf';
set newname for datafile 3 to '/ora01/db/ehr/sysaux01.dbf';
set newname for datafile 4 to '/ora01/db/ehr/undotbs02.dbf';
set newname for datafile 5 to '/ora01/db/ehr/users01.dbf';
set newname for datafile 6 to '/ora01/db/ehr/apolloaud01.dbf';
set newname for datafile 7 to '/ora01/db/ehr/apollohist01.dbf';
set newname for datafile 8 to '/ora01/db/ehr/apolloidx01.dbf';
set newname for datafile 9 to '/ora01/db/ehr/apollotab01.dbf';
set newname for datafile 10 to '/ora01/db/ehr/apollotab02.dbf';
set newname for datafile 11 to '/ora02/db/ehr/apollolob01.dbf';
set newname for datafile 12 to '/ora01/db/ehr/apollofdb01.dbf';
set newname for datafile 13 to '/ora01/db/ehr/apolloidx02.dbf';
set newname for datafile 14 to '/ora01/db/ehr/apolloidx03.dbf';
set newname for datafile 15 to '/ora01/db/ehr/apolloaud02.dbf';
set newname for datafile 16 to '/ora01/db/ehr/apollotab03.dbf';
set until sequence 60298 thread 2;
restore database;
switch datafile all;
recover database;
Datafile 11 is the datafile in the bigfile tablespace. Here are the weird things about the restore:
1. The restore output shows this:
creating datafile fno=11 name=/ora02/db/ehr/apollolob01.dbf
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /ora01/db/ehr/system01.dbf
restoring datafile 00002 to /ora01/db/ehr/undotbs01.dbf
restoring datafile 00003 to /ora01/db/ehr/sysaux01.dbf
restoring datafile 00004 to /ora01/db/ehr/undotbs02.dbf
restoring datafile 00005 to /ora01/db/ehr/users01.dbf
restoring datafile 00006 to /ora01/db/ehr/apolloaud01.dbf
restoring datafile 00007 to /ora01/db/ehr/apollohist01.dbf
restoring datafile 00008 to /ora01/db/ehr/apolloidx01.dbf
restoring datafile 00009 to /ora01/db/ehr/apollotab01.dbf
restoring datafile 00010 to /ora01/db/ehr/apollotab02.dbf
restoring datafile 00012 to /ora01/db/ehr/apollofdb01.dbf
restoring datafile 00013 to /ora01/db/ehr/apolloidx02.dbf
restoring datafile 00014 to /ora01/db/ehr/apolloidx03.dbf
restoring datafile 00015 to /ora01/db/ehr/apolloaud02.dbf
restoring datafile 00016 to /ora01/db/ehr/apollotab03.dbf
Why at the beginning is it "creating" datafile 11? Then it doesnt even say it is "restoring" that datafile. Only restoring datafiles 1,2,3,4,5,6,7,8,9,10,12,13,14,15, and 16.
When it creates datafile 11 it is only 26GB, that is much smaller than it should be according to v$datafile view on source prod database. Also even though it says it is creating datafile 11 as /ora02/db/ehr/apollolob01.dbf it actually creates it as an oracle managed file at /ora02/db/ehr/EHR/datafile/o1_mf_apollolo_6crxyqs2_.dbf
After the datafiles are restored the "switch datafile all" command fails:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of switch command at 10/18/2010 13:58:37
ORA-19625: error identifying file /ora02/db/ehr/apollolob01.dbf
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
So my question is how do I get this database restored to non-ASM (and non omf)?

So I tried using a different scn with my "set until scn #####" then the restore created 2 datafiles. The datafile for apollolob and apollotab02.dbf. So I think I have narrowed the problem to be that I am not using the correct scn number so RMAN can successfully restore those datafiles and recreates them instead. How do I find the correct scn to use to do a successful restore of the entire database? I have seen different methods on the web, but cant figure it out. Ive used "select archivelog_change#-1 from v$database;" and I also did "list backup of archivelog all" and used the latest sequence number. How can I find the correct scn to use so the entire database will restore?
Here is the output of "list backup":
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
19724 41.12M DISK 00:00:10 14-OCT-10
BP Key: 65840 Status: AVAILABLE Compressed: YES Tag: TAG20101014T210022
Piece Name: /mnt/migrate/rman/EHR_dbid3632734257_set113195_piece1_copy1_20101014
List of Archived Logs in backup set 19724
Thrd Seq Low SCN Low Time Next SCN Next Time
1 50439 3230234843 14-OCT-10 3230268282 14-OCT-10
1 50440 3230268282 14-OCT-10 3230286806 14-OCT-10
2 60280 3230234852 14-OCT-10 3230251419 14-OCT-10
2 60281 3230251419 14-OCT-10 3230268263 14-OCT-10
2 60282 3230268263 14-OCT-10 3230286809 14-OCT-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
19725 Full 126.40G DISK 09:11:51 15-OCT-10
List of Datafiles in backup set 19725
File LV Type Ckp SCN Ckp Time Name
1 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/system.625.609259453
2 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/undotbs1.620.609259461
3 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/sysaux.768.609259463
4 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/undotbs2.632.609259467
5 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/users.257.609259471
6 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloaud.316.619537285
7 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollohist.629.619538155
8 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.312.619538169
9 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.276.619538487
10 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.576.619539331
11 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollolob.570.619539593
12 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollofdb.750.645974339
13 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.429.651171265
14 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.705.688680793
15 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloaud.747.699632315
16 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.330.715622123
Backup Set Copy #1 of backup set 19725
Device Type Elapsed Time Completion Time Compressed Tag
DISK 09:11:51 20-OCT-10 YES TAG20101014T210039
List of Backup Pieces for backup set 19725 Copy #1
BP Key Pc# Status Piece Name
65851 1 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece1_copy1_20101014
65862 2 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece2_copy1_20101014
65873 3 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece3_copy1_20101014
65884 4 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece4_copy1_20101014
65895 5 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece5_copy1_20101014
65901 6 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece6_copy1_20101014
65902 7 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece7_copy1_20101014
65903 8 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece8_copy1_20101014
65904 9 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece9_copy1_20101014
65841 10 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece10_copy1_20101014
65842 11 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece11_copy1_20101014
65843 12 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece12_copy1_20101014
65844 13 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece13_copy1_20101014
65845 14 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece14_copy1_20101014
65846 15 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece15_copy1_20101014
65847 16 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece16_copy1_20101014
65848 17 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece17_copy1_20101014
65849 18 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece18_copy1_20101014
65850 19 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece19_copy1_20101014
65852 20 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece20_copy1_20101014
65853 21 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece21_copy1_20101014
65854 22 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece22_copy1_20101015
65855 23 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece23_copy1_20101015
65856 24 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece24_copy1_20101015
65857 25 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece25_copy1_20101015
65858 26 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece26_copy1_20101015
65859 27 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece27_copy1_20101015
65860 28 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece28_copy1_20101015
65861 29 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece29_copy1_20101015
65863 30 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece30_copy1_20101015
65864 31 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece31_copy1_20101015
65865 32 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece32_copy1_20101015
65866 33 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece33_copy1_20101015
65867 34 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece34_copy1_20101015
65868 35 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece35_copy1_20101015
65869 36 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece36_copy1_20101015
65870 37 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece37_copy1_20101015
65871 38 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece38_copy1_20101015
65872 39 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece39_copy1_20101015
65874 40 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece40_copy1_20101015
65875 41 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece41_copy1_20101015
65876 42 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece42_copy1_20101015
65877 43 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece43_copy1_20101015
65878 44 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece44_copy1_20101015
65879 45 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece45_copy1_20101015
65880 46 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece46_copy1_20101015
65881 47 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece47_copy1_20101015
65882 48 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece48_copy1_20101015
65883 49 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece49_copy1_20101015
65885 50 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece50_copy1_20101015
65886 51 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece51_copy1_20101015
65887 52 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece52_copy1_20101015
65888 53 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece53_copy1_20101015
65889 54 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece54_copy1_20101015
65890 55 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece55_copy1_20101015
65891 56 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece56_copy1_20101015
65892 57 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece57_copy1_20101015
65893 58 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece58_copy1_20101015
65894 59 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece59_copy1_20101015
65896 60 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece60_copy1_20101015
65897 61 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece61_copy1_20101015
65898 62 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece62_copy1_20101015
65899 63 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece63_copy1_20101015
65900 64 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece64_copy1_20101015
BS Key Size Device Type Elapsed Time Completion Time
19726 228.10M DISK 00:00:49 15-OCT-10
BP Key: 65905 Status: AVAILABLE Compressed: YES Tag: TAG20101015T061242
Piece Name: /mnt/migrate/rman/EHR_dbid3632734257_set113197_piece1_copy1_20101015
List of Archived Logs in backup set 19726
Thrd Seq Low SCN Low Time Next SCN Next Time
1 50441 3230286806 14-OCT-10 3230331993 14-OCT-10
1 50442 3230331993 14-OCT-10 3230401945 14-OCT-10
1 50443 3230401945 14-OCT-10 3230469794 15-OCT-10
1 50444 3230469794 15-OCT-10 3230555010 15-OCT-10
1 50445 3230555010 15-OCT-10 3230618396 15-OCT-10
1 50446 3230618396 15-OCT-10 3230695020 15-OCT-10
2 60283 3230286809 14-OCT-10 3230304858 14-OCT-10
2 60284 3230304858 14-OCT-10 3230330891 14-OCT-10
2 60285 3230330891 14-OCT-10 3230354275 14-OCT-10
2 60286 3230354275 14-OCT-10 3230366292 14-OCT-10
2 60287 3230366292 14-OCT-10 3230399805 14-OCT-10
2 60288 3230399805 14-OCT-10 3230423577 14-OCT-10
2 60289 3230423577 14-OCT-10 3230446176 15-OCT-10
2 60290 3230446176 15-OCT-10 3230469756 15-OCT-10
2 60291 3230469756 15-OCT-10 3230496786 15-OCT-10
2 60292 3230496786 15-OCT-10 3230524710 15-OCT-10
2 60293 3230524710 15-OCT-10 3230554981 15-OCT-10
2 60294 3230554981 15-OCT-10 3230583802 15-OCT-10
2 60295 3230583802 15-OCT-10 3230610465 15-OCT-10
2 60296 3230610465 15-OCT-10 3230617887 15-OCT-10
2 60297 3230617887 15-OCT-10 3230673207 15-OCT-10
2 60298 3230673207 15-OCT-10 3230695022 15-OCT-10

Can't create 11gR1 Database with 11gR2 CRS/ASM non RAC, dbca ASM password

Hi,
try to create a 11gR1 SE Database on a single server with 11gR2 ASM up and running.
when dbca ask where to store the datafiles and i choose ASM, i have to give the asm sys password which i know (can connect with sql+).
dbca replies wrong password and i can NOT go further.
is it possible to use 11gR2 ASM with 11gR1 database and create a database with dbca?
any hint for this situation?
thanks
Michael
Edited by: user12132314 on 18.07.2010 22:24

Hello,
i tried again - still don't work
it is dbca step 6 from 16, storage option (or something simiular - dbca lang here is german)
the dialog looks like this
ASM-ID-Data (Titel)
enter ASM specific SYS password (prompt)
entering the correct pwd and push OK
dbca shows a error dialog with something like: password for user SYS not valid. Enter a valid password.
Any help?
Michael

Issue with clearing the Differences in 999 storage type in HU managed S.Loc

Hi Experts,
We are trying to writeoff the differences stocks which are there in 999 storage type, but getting an error message 'Quantity difference document line item for HU's' with Message class L6 & Message number 606. Any idea how this can be resolved?
I can see that for this product/batch combination there is another HU in packing area 923 which is acting as a SU because the item level details are deleted for this HU. Could this be the issue for the errror? Would need some pointers to clear this stocks.
Thanks,
Harish

The item details of the HU seems to be have deleted, causing the difference between HU, IM/WM stocks. We have deleted the HU using HUMO & then the HU difference quantity was posted using HUDIFF.
Thanks,
Harish

Regard an error "Storage type & notsuitable as interface (SU mgmt is active

Hi All,
I am trying to do the inventory clearing in both warehouse and Inventory management using the transactions LI20 and LI21 after counting the inventory. But whenever I am trying to do the writeoff's I am facing with an error "Storage type & not suitable as an interface (SU management is active)"
I couldnt able to figure out the main cause for this error. Your valuable suggestions would be highly appreciated.
Regards,
Shane

Hi Jürgen L,
My objective is to do physical inventory and of ther are any differences then write them........in this sytem Both Grants and fund management is involved?
I am getting this message while I am doing LI21. And you have suggested that, the difference storage type SU managed. which is a 999 storage type. and this is not SU managed.
I would also like to ask regarding the clearing of differences in warehouse and Inventory mangement. I am using the mvmt types 711 and 712, But what account documents will get generated. I am thinking there will be no account documents that will get generated. Adding to this I am getting "Account 6701 requires an assignment to a CO object with Message no. KI235". If we do this assignment to this CO object......... doesnt the transaction go and hit the balance sheet account.
I am lil baffled with this whole process. If you could give me your valuable information, that will help me a lot.
Shane.

ORA-39070 Error when using datapump and writing to ASM storage

I am able to export data using datapump when i write to a file system. However, when i try to write to an ASM storage, i get the following errors.
ORA-39002: invalid operation
ORA-39070: Unable to open the log file.
ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 536
ORA-29283: invalid file operation
below are the steps i tooks.
create or replace directory jp_dir2 as '+DATA/DEV01/exp_dir';
grant read,write on directory jp_dir2 to jpark;
expdp username/password schemas=testdirectory=jp_dir2 dumpfile=test.dmp log=test.log
Edited by: user564785 on Aug 25, 2011 6:49 AM

google: expdp ASM
first hit:
http://asanga-pradeep.blogspot.com/2010/08/expdp-and-impdp-with-asm.html
"Log files created during expdp cannot be stored inside ASM, for log files a directory object that uses OS file system location must be given. If not following error will be thrown
ORA-39002: invalid operation
ORA-39070: Unable to open the log file.
ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 536
ORA-29283: invalid file operation
"

Error - No destination storage bin to be found in storage type

Hi all,
this is my flow -
Create STO PO - ME21n
create deliveries via - BAPI_OUTB_DELIVERY_CREATE_STO
create Transfer order(TO) - L_TO_CREATE_DN - for o/b delivery
confirm TO- L_TO_CONFIRM
Using BDC i am doing PGI for VL02n
create Transfer order(TO) - L_TO_CREATE_DN - for i/b delivery
confirm TO- L_TO_CONFIRM
Create GR - 'BAPI_GOODSMVT_CREATE'
Here till PGI my report pgm is working fine. and when cominf to TO create based on i/b delivery i am getting error -
No destination storage bin to be found in storage type 104
I have added 2 lines in the FM at exception part -
error_message = 16
OTHERS = 32.
So my return code for the FM - L_TO_CREATE_DN (_FOR i/b delivery)_is 16
message class : L3
message number : 009
message type : E
No destination storage bin to be found in storage type 104
Can any one tell me how can be this rectified - Is this a config related issue or data problem ?
Pls help me.
Sen

Hi all,
Thanks for your replies.
Manish: Where do I see that the storage bin is created with respect to storage type? I was checking LS03N where I can see that the storage bin is created for storage section and storage bin type. Configuraiton is like below:
Storage Bin search Strategy:
(1) By storage section: Not active
(2) By Stotage Bin type - Active and the storage bin type is assigned to a storage type.
I have one storage bin available (Bulk Storage) for the selected storage Bin type BUT it is not automatically searched by the process. Material master has WM view1 with storage type indicator and there is a config for storage type search which is working good. The only issue is searching storage bin while creating TO during Goods movement, in particular Put away. Also please note that the storage bin is not hardcodes in material master).
This error happens for all the scenarios (unrestricted, blokced or when WM stock is initial or when the materrial is created first time and subject the WM movements).
When I first started this question I thought that the error happens only for Blocked status. Actually it is happening for all the scenatios when the WM stock in initial.
Hope my scenarios are clear. Thanks in advance for your help again.
Best regards
Nagarajan

Error with dbca -silent ASM storage type

Similar Messages

Maybe you are looking for