Record stall errors

I'm running Logic Pro 8 on a MacBook Pro 15-inch 2.4 4 gig ram, 250 gig 7200. Accompanied by a Lacie D2 7200 1TB
I'm recording concerts for archive consisting 48 tracks (46 mono 2 Stereo) @ 48k over about 90 minutes.
I have been receiving errors causing stalls in the recording. The main 2 I have ran into are;
1) Some kind of MIDI sync error, could only resolve with re boot. I have no need for MIDI
not entirely sure of error, if someone could direct me to the correct log maybe?.....
2) Disk too slow.
I have had this when recording to both the internal and external drives.
The disk usage meter can drag at 80% one day and be at 0% the next with no reasoning at all, again either recording to the internal or external.
Is there anymore information I can offer you to try and resolve these snags?
Any suggestions to what I could change to resolve these issues?
Many thanks in advance.

Oliver Waring wrote:
thanks Pancenter.
The external drive does have journaling on, but would that explain the >irregular disk usage? i.e. if journaling is on is it not on all the time?
Yes, it could explain some of it.
You don't need to reformat to disable journaling.
See Erik's excellent example in this thread.
http://discussions.apple.com/thread.jspa?threadID=1970429&tstart=0
Trust me, you need to disable journaling on the 1TB drive.
Also, definitely try the different size "process buffers". In some situations a smaller process buffer works best.
You aren't using any plugins during recording, correct?
Is there a way to prevent the MIDI sync error? previously the only way I've been able to resolve that is a complete reboot. In a live show every second counts.....
It can be related to several things, an overloaded Firewire bus, even the high disk usage. Any number of errors can knock the audio/MIDI engine out of sync.
One thing at a time, disable journaling on the 1TB drive.
What audio hardware are you using?
pancenter-

Similar Messages

How to edit the records in error stock.

Hi Experts,
i have error records in error stack and the remaining records are loaded successfuly . here my doubt is how to edit the records in error stack because its not giving the edit option .
i want to get the edit option means i need to delete the request in target r wt ?
and there are two more targets is there below this process .
Advance Thanks.
Regards
SAP

HI
If you have less number records in this request(which you extracted now), delete that request from all the targets and reload again with option Valid records update, reporting not possible.
this is the option which is recommended.
follow the below 2 docs as well.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80dd67b9-caa0-2e10-bc95-c644cd119f46?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/007f1167-3e64-2e10-a798-e1ea456ef21b?QuickLink=index&overridelayout=true
Regards,
Venkatesh
Edited by: Venkateswarlu Nandimandalam on Jan 24, 2012 4:35 PM

Error in ST05 - trace record pair error block. How to resolve/tackle issue?

Hello,
Someone approached me last week in asking me how to resolve an issue in ST05. Basically I used the transaction to filter "inclusive VBPA".
The error is ....
Internal error - trace record pair error block 8 link no. 0
Message no. 0S 026
Diagnosis
    Each SQL statement is described by two SQL trace records that have the
    same link number. In this case, there are at least three records with the
    same link number.
    The system outputs the number of the block in which the third SQL trace
    record was found, as well as the link number of the records.
System response
    Program processing continues after the message is displayed. The system
    processes all of the trace records. You should assume, however, that the
    SQL trace in this case is not displayed correctly.
Procedure
You cannot correct this error yourself. If you can reproduce the error,
contact the SAP Hotline.
SQL trace list editing terminated after 6 errors
While using the trace I am executing the program that selects VBPA once and, I am assuming, as it goes through the BAPI BAPI_SALESORDER_CHANGE used to unblock a delivery block. I am guessing the problem or source is from the BAPI but do you guys have other insights in what is causing this issue?
Thanks again, hope to hear from you soon, and good day.

Our ERP LIVE Production around 11am all users encountered cannot generate print record from the submit new request. see below errorFor production issues, please log a SR.
ORA-00060: Deadlock detected. More info in file /u/oracle/PROD/db/tech_st/11.1.0/admin/PROD_tailindb/diag/rdbms/prod/PROD/trace/PROD_ora_4026.trc.
ORA-00060: Deadlock detected. More info in file /u/oracle/PROD/db/tech_st/11.1.0/admin/PROD_tailindb/diag/rdbms/prod/PROD/trace/PROD_ora_4026.trc.
ORA-00060: Deadlock detected. More info in file /u/oracle/PROD/db/tech_st/11.1.0/admin/PROD_tailindb/diag/rdbms/prod/PROD/trace/PROD_ora_4026.trc.Please see these docs.
OERR: ORA 60 "deadlock detected while waiting for resource" [ID 18251.1]
What to do with "ORA-60 Deadlock Detected" Errors [ID 62365.1]
Thanks,
Hussein

Edit the error records in error stack

Hi,
I want to edit the error records in error stack. There are around 300 records in error stack . I want to replace the value in one field with blank to correct the records. Can you please help me how to replace the value with blank.
Thanks,
Priya

Hi,
Open the original DTP and click on change.
1) In Update you will find "create error DTP", just click on it system automatically create error DTP for you original DTP.
2) Do not change any thing, just come back to your original DTP and activate your DTP again.
Now come back and refresh the info provider tree.
now execute your DTP, request will be green in target and you will error records in error stack.
How to edit the error records in error DTP
please find the doc.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0406328-29c7-2e10-5db5-afe9b5695eeb?overridelayout=t…
Thanks,
Phani.

Sql loader (catching record length error)

Guys is there any command in sqlldr that can catch record length error (less or more than certain length).I am using java to execute my sqlldr and would like to know if it is possible to catch those error.
thanks
Manohar.

Use CHAR instead aof VARCHAR
LOAD DATA
INFILE *
APPEND INTO TABLE test
FIELDS TERMINATED BY ','
OPTIONALLY ENCLOSED BY '"'
first_id,
second_id,
third_id,
language_code,
display_text CHAR(2000)
)From the docu:
A VARCHAR field is a length-value datatype.
It consists of a binary length subfield followed by a character string of the specified length.
http://download-west.oracle.com/docs/cd/A87860_01/doc/server.817/a76955/ch05.htm#20324

Record 1 :Error in a formula function (routine ROUTINE_0001 ), record 1

Hi ALL,
i ran the infopackge.load was failed.failed request is showing Record 1 :Error in a formula function (routine ROUTINE_0001 ), record 1 .why this error is coming.how can i solve this issue?
Thanks,
chandu

Hi Chandra,
Must be error in transfer rules. Conversion error in transfer routine or format error in file.If it is go to debugger and check.
Hope you have got the hint
thanks
udaykiran

Officejet pro 8600 Premium pick motor stalled error message

I have the Officejet Pro 8600 Premium printer. I'm getting the message "pick motor stalled" after two and a half months of stellar use with this printer. There is no paper/print jam. I'm using the same paper I have always used. Help, is this a problem with this model?

Also having this issue with an Officejet Pro 8600 Premium too. Bought it in May 2012 to replace an Officejet 7410. Running on a wireless network to a Win 7 32 bit laptop. Started getting the popular Pick Motor Stalled error after two months of ownership of the 8600. Have been able to get the printer to reset this error in the past with combinations of powering down, running diagnostics, and having the printer execute either a print head clean routine or a print printer status routine - that is up until this weekend. Trying to print tax returns so I can get them in the mail by the 4/15 deadline tomorrow and, of course, the Pick Motor Stalled error shows up again. Spent several hours trying usual tricks, this time nothing works. Finally, as a desperate last resort, I powered down the printer and completely removed the second printer tray assembly from the bottom of the printer. Powered back up running only the single main tray and that did the trick. Printing restored.For those that might conclude there was a paper jam on the machine and removing the second paper tray assembly fixed it, trust me. I have been in and out of that machine. There was no paper jam. There is some glitch in either the electronics or firmware, or both on these printers that is causing all the Pick Motor Stalled errors that the user community for this HP device has been dealing with.

Status record 65 error in ale service

HI Experts,
               I have an issue when I tried to send a cost center idoc from one system to another. The company code for the record is 0093 in the sender system; however when the idoc gets created, in the idoc the value of the company code becomes SAH001. I dont know why this happens.
This is the record to in the corresponing table table- which is to be sent from sender to Receiver. The company code ie company code field value is 0093 .
The RFC/LS connections have been done and checked. I am able to send the cost center group data correctly. While sending the cost center I am encountering the following error:-
For an example
Content of created Idoc in sender
Company code field |   SAH001
The company code info is now SAH001. I wonder why ?
So when we send the idoc to recceiver, we get the same company code and I get an error that company code doesnt exist.
Content of idoc in receiver
Company code field |   SAH001
I want to display 0093.
Please tel me what is error and how to rectify?
Thanks & regards
Mathi

hI,
Testing inbound idoc :
Once you configured everything then goto WE19 Transaction :
Give message type or idoc type and execute .
now here you need to fill the Mandatory data in each segment,once you done then
idoc->edit control record -> here you need to fill sender and receiver details.
now you should get green color ,if you get red color then config issue.
now click on start inbound -> now you will get idoc number.
if you want to debug then click on inbound function module -> enter FM -> select call in debug mode and enter.
now cursor will go debug mode
http://www.photographybykevin.net/sap/idoc_overview.pdf
Testing Outbound idoc :
Once you done all configuration ..
Let me say example like invoice ,you need to send invoice from SAP R/3 to other system.
create invoice at VF01 -> Here customer should configure in Parter profile ,once you create invoice ,it creates the idoc.
debugging Outbound IDOC :
keep the break point in form routine above as i said
Create invoice or invoice list
when you maintain output type in invoice or invoice list -
Now click on Further data ->select peridoc scheduling-> back and save it.
Run RSNAST00 Program
Output application : V3
Object key : Invoice or invoice list number
Output type : RD00 or LR00
Medium = 6(EDI) ,A (ALE)
when you execute the program and it will goto debugging.
See the below status codes :
See table TEDS1 for all status codes via SE16 in SAP. Outbound ALE Status Codes
Successful Transmission:
03 - Successful outbound transmission
12 - Dispatch OK
IDoc being processed:
01 - IDoc created
30 - IDoc ready for dispatch (ALE service) (Program RSEOUT00 needs to be executed)
ALE Error Messages:
02 - Error passing data to port
04 - Error within control information on EDI subsystem
05 - Error during translation
25 - Processing despite syntax errors (outbound)
29 - Error in ALE service
32 - Resubmit edited intermediate document (DO NOT USE)
Syntax Error Messages:
26 - Error during syntax check of IDoc (outbound) Inbound ALE Status Codes
IDoc Processed Successfully:
50 - IDoc added
53 - Successful posting
IDoc ready for processing:
64 - IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.
Errors in IDoc Processing:
51 - Error - application document not posted
56 - IDoc with errors added (You should never see this error code)
60 - Error during syntax check of IDoc (inbound)
61 - Processing despite syntax error (inbound)
63 - Error passing IDoc to application
65 - Error in ALE service - indicates partner profiles are incorrect
69 - IDoc was edited
Regards,
Nagaraj

Disk is too slow (Record)(-10004) error..so sick of this.

Hello all,
I can no longer record more than three tracks in logic without getting the error message "Disk is too slow (Record)(-10004)". When this happens, recording is stopped.
At first I suspected my drive was faulty, maybe slowing down. So being in the middle of a session that took me 2 hours to set up, I called for a break and rushed off and bought an external Seagate 7200rpm firewire 800 drive. I installed it and set it as the recording path for the project. There was no change, the same error occured.
I then switched the target drive to another internal one I use for Time Machine - same problem occured.
It seems to me that this problem has nothing to do with my drives. I am at a loss to explain it. I have looked for hours online for a solution but while many have experienced this there seem to be few answers out there.
Unless I find a solution this will be my last project with Logic. I tried and tried for the last 5 years to use this program but things like this keep happening. It's glitchy with UAD cards, Duende, RME interfaces, Midi controllers, Hard Drives, RAM and external clocks. I've had problems with them all over the years. I will most likely switch to Cubase which I feel is inferior for editing and loops, but at least it seems to be stable.
If anyone has any insight I'll try and fix it, but I just can't keep shelling out money for a program that just doesn't work.

I am experiencing a similar problem & have been receiving the same messages, even while recording as little as one track and playback has become an issue as well. However, THIS WAS NOT ALWAYS THE CASE. I have heard of people with this same problem, where they receive this message out of nowhere after logic has been working perfectly for them.
I also would like to note that I am running all settings in logic for optimized recording and playback (audio & buffer settings etc etc etc)
THIS IS NOT A HARDWARE ISSUE, at least in my situation as I am running a fast internal HD & have ample memory. Please reach out if you feel like you have a pragmatic solution to this issue.
This may be a possible lead on the fix... I remember reading this post from a user "soundsgood" in 2008 who was having a similar issue..I don't understand completely his solution, but if someone could enlighten me, I feel that this might be the solution to our issue
+"Okay - forgive me 'cause I'm a newbie on this forum and if somebody else has already figgered this out, I'm sorry.... I've been having the same problem all of the sudden after many years of crash-free and error-free recording. I've read everything. I've pulled my hair out. I've done dozens of clean installs. I've repaired permissions so many times I can do it blindfolded. And sitting here tonight, it dawned on me.... there are TWO places Logic is sucking data from: wherever you've got your SONG files stashed, of course.... but it ALSO NEEDS TO ACCESS THE STARTUP DRIVE (or wherever else you might have your Apple Loops installed). I was watching my drives being accessed during a playback of a fairly complicated tune (most tracks were frozen of course), and both of the afore-mentioned drives were going berserck with accesses. We're all focusing on our dedicated audio drives, but forgetting about our boot drives (where Logic usually resides along with most or all of our loops). I carbon copy cloned my boot / operating system (including Logic) to a different (in my case, an external firewire) drive and the problem disappeared. Could've been because the cloning process de-fragged all the loops & stuff, or maybe my OS just likes snatching its sample/loop info from an external drive. Worked for me... so far....... let me know if it works for others....."+

SQL*Loader- Records Rejected - Error on table ORA-01722: invalid number

Getting the following errors :
Please tell me where I am going wrong?
Attached is the log file and snippets of datafile along with the control file !!
Also please direct me how can i upload 4900 records at one go?
SQL*Loader: Release 11.1.0.7.0 - Production on Fri Oct 14 03:06:06 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Control File: sample.ctl
Data File: Cities.csv
Bad File: Cities.bad
Discard File: none specified
(Allow all discards)
Number to load: ALL
Number to skip: 0
Errors allowed: 50
Bind array: 64 rows, maximum of 256000 bytes
Continuation: none specified
Path used: Conventional
Table CITY, loaded from every logical record.
Insert option in effect for this table: INSERT
Column Name Position Len Term Encl Datatype
ID FIRST * , CHARACTER
NAME NEXT 35 , ' CHARACTER
COUNTRYCODE NEXT 3 , ' CHARACTER
POPULATION NEXT * WHT CHARACTER
Record 1: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 2: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 3: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 4: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 5: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 6: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 7: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 8: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 9: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 10: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 11: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 12: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 13: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 14: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 15: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 16: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 17: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 18: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 19: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 20: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 21: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 22: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 23: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 24: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 25: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 26: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 27: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 28: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 29: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 30: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 31: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 32: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 33: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 34: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 35: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 36: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 37: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 38: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 39: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 40: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 41: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 42: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 43: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 44: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 45: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 46: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 47: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 48: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 49: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 50: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
Record 51: Rejected - Error on table CITY, column POPULATION.
ORA-01722: invalid number
MAXIMUM ERROR COUNT EXCEEDED - Above statistics reflect partial run.
Table CITY:
0 Rows successfully loaded.
51 Rows not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were failed.
0 Rows not loaded because all fields were null.
Space allocated for bind array: 35840 bytes(64 rows)
Read buffer bytes: 1048576
Total logical records skipped: 0
Total logical records read: 64
Total logical records rejected: 51
Total logical records discarded: 0
Run began on Fri Oct 14 03:06:06 2011
Run ended on Fri Oct 14 03:06:12 2011
Elapsed time was: 00:00:06.18
CPU time was: 00:00:00.03
my control file (sample.ctl):
load data infile 'Cities.csv'
into table city
fields terminated by ','
(id integer external,
name char(35) enclosed by "'",
countrycode char(3) enclosed by "'",
population integer external terminated by '\n'
my datafile (Cities.csv) (it contains 4900 records, but I am showing here just 4 records for ease)
3830,'Virginia Beach','USA',425257
3831,'Atlanta','USA',416474
3832,'Sacramento','USA',407018
3833,'Oakland','USA',399484
Thanks in advance!!

Look that when I change a little bit your datafile as follows
1,'Kabul','AFG',1780000
2,'Qandahar','AFG','237500'
3,'Herat','AFG','186800' I got the same error (2 last rows rejected for the same error invalid number)
mhouri > select * from cities;
        ID NAME                                COU POPULATION
         1 Kabul                               AFG    1780000
SQL*Loader: Release 10.2.0.3.0 - Production on Fri Oct 14 10:38:06 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Control File:   cities.ctl
Data File:      cities.dat
Bad File:     cities.bad
Discard File: none specified
(Allow all discards)
Number to load: ALL
Number to skip: 0
Errors allowed: 50
Bind array:     64 rows, maximum of 256000 bytes
Continuation:    none specified
Path used:      Conventional
Table CITIES, loaded from every logical record.
Insert option in effect for this table: INSERT
   Column Name                  Position   Len Term Encl Datatype
ID                                  FIRST     *   ,       CHARACTER
NAME                                 NEXT    35   ,    ' CHARACTER
COUNTRYCODE                          NEXT     3   ,    ' CHARACTER
POPULATION                           NEXT     * WHT      CHARACTER
Record 4: Rejected - Error on table CITIES, column ID.
Column not found before end of logical record (use TRAILING NULLCOLS)
Record 2: Rejected - Error on table CITIES, column POPULATION.
ORA-01722: invalid number
Record 3: Rejected - Error on table CITIES, column POPULATION.
ORA-01722: invalid number
Table CITIES:
1 Row successfully loaded.
3 Rows not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were failed.
0 Rows not loaded because all fields were null.
Space allocated for bind array:                  35840 bytes(64 rows)
Read   buffer bytes: 1048576
Total logical records skipped:          0
Total logical records read:             4
Total logical records rejected:         3
Total logical records discarded:        0
Run began on Fri Oct 14 10:38:06 2011
Run ended on Fri Oct 14 10:38:06 2011
Elapsed time was:     00:00:00.23
CPU time was:         00:00:00.09Population value within the data file should be a number
Best regards
Mohamed Houri

Delete Record, Javascript error

Hi everyone
Just wondering if you can help. I am getting 2 javascript errors in dreamweaver when I try to enter a delete record using server behaviour.
They are (in order they appear)
While executing onblur in DeleteRecord.htm, the following javascript error(s) occured:
In file "DeleteRecord":
updateUI is not defined
Then when I click OK, i get the following
While executing onblur in DeleteRecord.htm, the following javascript error(s) occured:
In file "DeleteRecord":
initializeUI is not defined
This is happening in all sites and pages.
I have rebuilt the local configeration files and recreated DAT file etc but am now out of ideas.
Anyone know of a solution for this??
Much thanks in advance.

Here's the full KB article. Start with 12 & 4 and then go through the rest. One of those is always the answer:
http://helpx.adobe.com/dreamweaver/kb/troubleshoot-javascript-errors-dreamweaver-cs4.html

Delete Record Checksum Error

I am using the Issue Tracker App and when I try to delete and issue I get the following message:
Error print success message checksum content error: Action Processed./5535B61EFE9BB4ED531393FB89E0DC59/ : 74C582E81C9C0EAA3625984CA9D27CAD
It deletes the record, but doesnt display the right message.
Any ideas on what the problem is?
Thanks!!!

Hi Scott,
Thanks for your reply. I am new to HTML DB but will try to answer all your questions...
1- How do I do that?
2- I added an extra field to the ht_issues table.
3-
Database Banner
Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - 64bi
PL/SQL Release 10.1.0.2.0 - Production
CORE 10.1.0.2.0 Production
TNS for Solaris: Version 10.1.0.2.0 - Production
NLSRTL Version 10.1.0.2.0 - Production
NLS_CHARACTERSET WE8ISO8859P1
DAD CHARACTERSET ISO-8859-1
4- This is the URL...
http://sydupgd01.qantas.com.au:7777/pls/htmldb/f?p=115::13691776009622899511::NO:::&success_msg=Action%20Processed.%2F7A96B385753E175B892EC42FD7CCC691%2F

Recording device error on DVD DL -HELP!

Hi there,
I have problems burning a Dual Layer DVD with DVDSP 4. I'm using DVD+R DL Verbatim as the media in a DVD-RW DVR-111D. But it keeps sending the following message:
"Recording device reported the media error: Unknown device error (0x73,0x03.)"
I've tried direct from SP and with Roxio Toast v. 6.1.1.
Any idea what's going on?
Comments and suggestions are welcome!
Desperate Marissa =(

What speed disc are you using? That burner will only burn speeds up to 8x for DL. You might also try burning at the slowest possible speed.

How to update more than 5 million records without error message ORA-00257:

Hi ,
I need to update some columns in my table which is contains about 5 million records
I 've already tried this
Update AAA_CDR
Set RoamFload = Null ;
but the problem is I've got the error message ("ORA-00257: archiver error. Connect internal only,until freed.) and the update consuming about 6 hours with no results ,
then I do the commands ( Alter system set db_recovery_file_dest_size=50G) and the problem solved .
but I need to update about 15 columns of this table to be null ,what I should do to overcome this message and update the table in reasonable time
Please Help Me ,

The best way would be to allocate sufficient disk space for your archive log destination. Your database is not sized properly. NOLOGGING option will not do much for you because it' only applies to direct load operations when the data inserted into nologging table is selected from another table. UPDATE will be be logged, regardless of the NOLOGGING status. Here is the quote from the manual:
<quote>
LOGGING|NOLOGGING
LOGGING|NOLOGGING specifies that subsequent Direct Loader (SQL*Loader) and direct-load
INSERT operations against a nonpartitioned index, a range or hash index partition, or
all partitions or subpartitions of a composite-partitioned index will be logged (LOGGING)
or not logged (NOLOGGING) in the redo log file.
In NOLOGGING mode, data is modified with minimal logging (to mark new extents invalid
and to record dictionary changes). When applied during media recovery, the extent
invalidation records mark a range of blocks as logically corrupt, because the redo data
is not logged. Therefore, if you cannot afford to lose this index, you must take a backup
after the operation in NOLOGGING mode.
If the database is run in ARCHIVELOG mode, media recovery from a backup taken before an
operation in LOGGING mode will re-create the index. However, media recovery from a backup
taken before an operation in NOLOGGING mode will not re-create the index.
An index segment can have logging attributes different from those of the base table and
different from those of other index segments for the same base table.
</quote>
If you are really desperate, you can try the following undocumented/unsupported command:
ALTER DATABASE ARCHIVELOG COMPRESS ENABLE;
That will cause database to compress your archive logs and consume less space. This command is not documented or supported, not even in the version 11.2.0.3 and causes the database to start spewing ORA-0600 in version 10G. DO NOT USE IN A PRODUCTION ENVIRONMENT!!!!

Recording device error#8

Anyone know how to correct this issue? Cannot burn DVD.
Starting DVD Build JOHNLORNA...
Compiler Initializing...
Precompiling Project JOHNLORNA
Compiling VMG Information...
Created 31 PGCs in VTSM1
Created 5 PGCs in VTSM2
Created 5 PGCs in VTSM3
Created 8 PGCs in VMG.
4 Menu(s) will be created...
Compiling Menu PGCs...
Compiling Menu#1 (Menu 1)...
Rendering Menu:Menu 1,Language:1...
Compiling Menu#2 (Menu 2)...
Rendering Menu:Menu 2,Language:1...
Compiling Menu#3 (Menu 3)...
Rendering Menu:Menu 3,Language:1...
Compiling Menu#4 (Menu 4)...
Rendering Menu:Menu 4,Language:1...
Generating Transition: VTSM #01, VOB #1...
Generating Transition: VTSM #01, VOB #2...
Generating Transition: VTSM #01, VOB #3...
Generating Transition: VTSM #01, VOB #4...
Generating Transition: VTSM #01, VOB #5...
Generating Transition: VTSM #01, VOB #6...
Generating Transition: VTSM #01, VOB #7...
Generating Transition: VTSM #01, VOB #8...
Generating Transition: VTSM #01, VOB #9...
Generating Transition: VTSM #01, VOB #10...
Generating Transition: VTSM #01, VOB #11...
Generating Transition: VTSM #01, VOB #12...
Generating Transition: VTSM #01, VOB #13...
Generating Transition: VTSM #01, VOB #14...
Generating Transition: VTSM #01, VOB #15...
Generating Transition: VTSM #01, VOB #16...
Generating Transition: VTSM #01, VOB #17...
Generating Transition: VTSM #01, VOB #18...
Generating Transition: VTSM #01, VOB #19...
Generating Transition: VTSM #01, VOB #20...
Generating Transition: VTSM #01, VOB #21...
Writing VIDEO_TS.VOB
Compiling Menu PGCs...
Writing VTS020.VOB
Compiling Menu PGCs...
Writing VTS030.VOB
3 VTSs and 3 Titles will be created...
Compiling VTS#1 (Ceremony (Video))...
Muxing VTS011.VOB
Done.
Compiling VTS#2 (Reception (Video))...
Writing VTS020.VOB
Muxing VTS021.VOB
Done.
Compiling VTS#3 (intro (Video))...
Writing VTS030.VOB
Muxing VTS031.VOB
Done.
Linking VMG...
Linking VTS#1...
Linking VTS#2...
Linking VTS#3...
Writing VTS#1...
Writing VTS#2...
Writing VTS#3...
Writing VMG...
Writing Layout Info...
Compile Completed Successfully
Warning: The file JOHNLORNA.layout found in the VIDEO_TS folder will not be included in the final disc.
Warning: The file VOB_DATA.LAY found in the VIDEO_TS folder will not be included in the final disc.
Start formatting
Formatting as Standard DVD
Simulation mode is off
Lossless linking is on
Number of layers is 1
Doing side 1 of 1
Playable in region 1,2,3,4,5,6,8
Disc size is 12 cm
Disc has no copyright material.
Writing ISO directories
Writing UDF structures
Writing files
The recording device reported the error #8: No additional sense information. (0x00, 0x00.)
The recording device reported the error #8: No additional sense information. (0x00, 0x00.)

Figured out what you meant and it finished successfully...here is the log. Now what do I do to burn the DVD? Thanks so much for your help.
Jon
Starting DVD Build JOHNLORNA...
Compiler Initializing...
Precompiling Project JOHNLORNA
Compiling VMG Information...
Created 31 PGCs in VTSM1
Created 5 PGCs in VTSM2
Created 5 PGCs in VTSM3
Created 8 PGCs in VMG.
4 Menu(s) will be created...
Compiling Menu PGCs...
Compiling Menu#1 (Menu 1)...
Rendering Menu:Menu 1,Language:1...
Compiling Menu#2 (Menu 2)...
Rendering Menu:Menu 2,Language:1...
Compiling Menu#3 (Menu 3)...
Rendering Menu:Menu 3,Language:1...
Compiling Menu#4 (Menu 4)...
Rendering Menu:Menu 4,Language:1...
Generating Transition: VTSM #01, VOB #1...
Generating Transition: VTSM #01, VOB #2...
Generating Transition: VTSM #01, VOB #3...
Generating Transition: VTSM #01, VOB #4...
Generating Transition: VTSM #01, VOB #5...
Generating Transition: VTSM #01, VOB #6...
Generating Transition: VTSM #01, VOB #7...
Generating Transition: VTSM #01, VOB #8...
Generating Transition: VTSM #01, VOB #9...
Generating Transition: VTSM #01, VOB #10...
Generating Transition: VTSM #01, VOB #11...
Generating Transition: VTSM #01, VOB #12...
Generating Transition: VTSM #01, VOB #13...
Generating Transition: VTSM #01, VOB #14...
Generating Transition: VTSM #01, VOB #15...
Generating Transition: VTSM #01, VOB #16...
Generating Transition: VTSM #01, VOB #17...
Generating Transition: VTSM #01, VOB #18...
Generating Transition: VTSM #01, VOB #19...
Generating Transition: VTSM #01, VOB #20...
Generating Transition: VTSM #01, VOB #21...
Writing VIDEO_TS.VOB
Compiling Menu PGCs...
Writing VTS020.VOB
Compiling Menu PGCs...
Writing VTS030.VOB
3 VTSs and 3 Titles will be created...
Compiling VTS#1 (Ceremony (Video))...
Muxing VTS011.VOB
Done.
Compiling VTS#2 (Reception (Video))...
Writing VTS020.VOB
Muxing VTS021.VOB
Done.
Compiling VTS#3 (intro (Video))...
Writing VTS030.VOB
Muxing VTS031.VOB
Done.
Linking VMG...
Linking VTS#1...
Linking VTS#2...
Linking VTS#3...
Writing VTS#1...
Writing VTS#2...
Writing VTS#3...
Writing VMG...
Writing Layout Info...
Compile Completed Successfully
Warning: The file JOHNLORNA.layout found in the VIDEO_TS folder will not be included in the final disc.
Warning: The file VOB_DATA.LAY found in the VIDEO_TS folder will not be included in the final disc.
Start formatting
Formatting as Standard DVD
Simulation mode is off
Lossless linking is off
Number of layers is 1
Doing side 1 of 1
Playable in region 1,2,3,4,5,6,8
Disc size is 12 cm
Disc has no copyright material.
Writing ISO directories
Writing UDF structures
Writing files
Writing final UDF information
Formatting finished.
Formatting finished.

Record stall errors

Similar Messages

Maybe you are looking for