Warnings: deprected

Hi, when I compile a java file , that uses Cortona package , it doesn't me syntax errors but warnings like this:
c:\Bluej\examples\esEAI\AddRemoveTest.java:7:warning:
[ deprecation ]vrml.external.Node in vrml.external has been deprecated.
So, I can with a sinple html file launch my applet but I can't visualizate anithing. What can I do to eliminate this warning?
Thanks and excuse me for my English. Hello

I see if a class is deprecated in java api?You see it in the API docs for said class, or directly in the source if you have access to it.
But wrml classes aren't here.
Where I can see?Indeed, "wrml classes" aren't part of the Java API. I don't know those classes; you do, since you're using them. So I would assume you also know where to find their documentation - presumably from the same web site where you downloaded the binaries.

Similar Messages

Unit Testing, Null, and Warnings

I have a Unit Test that includes the following lines:
Dim nullarray As Integer()()
Assert.AreEqual(nullarray.ToString(False), "Nothing")
The variable "nullarray" will obviously be null when ToString is called (ToString is an extension method, which is the one I am testing). This is by design, because the purpose of this specific unit test is to make sure that my ToString extension
method handles null values the way I expect. The test runs fine, but Visual Studio 2013 gives includes the following warning:
Variable 'nullarray' is used before it has been assigned a value. A null reference exception could result at runtime.
This warning is to be expected, and I don't want to stop Visual Studio 2013 from showing this warning or any other warnings, just this specific case (and several others that involve similar scenarios). Is there any way to mark a line or segment
of code so that it is not checked for warnings? Otherwise, I will end up with lots of warnings for things that I am perfectly aware of and don't plan on changing.
Nathan Sokalski [email protected] http://www.nathansokalski.com/

Hi Nathan Sokalski,
Variable 'nullarray' is used before it has been assigned a value. A null reference exception could result at runtime.
Whether the warning above was thrown when you built the test project but the test run successfully? I assume Yes.
Is there any way to mark a line or segment of code so that it is not checked for warnings?
There is no built-in way to make some code snippet or a code line not be checked during compiling, but we can configure some specific warnings not to be warned during compiling in Visual Basic through project Properties->Compile
tab->warning configurations box.
For detailed information, please see: Configuring Warnings in Visual Basic
Another way is to correct your code logic and make sure the code will not generate warning at runtime.
If I misunderstood you, please tell us what code you want it not to be checked for warnings with a sample so that we can further look at your issue.
Thanks,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Kernal warnings in Solaris 10

Dear Folks,
We have Solaris 10 box connected to HP SAN EVA8000 through dual HBA with MPXIO enabled. From quite some time we started receiving below warning messages, Any body Could explain, What is the reasons for these warnings or any solution to avoid them.....Many Thanks In Advance....
/var/adm/messages (scanned at Tue May 8 08:46:12 AST 2007)
May 8 08:44:33 mx-jes-11 fp: [ID 517869 kern.info] NOTICE: fp(0): PLOGI to 11400 failed state=Packet Transport error, reason=No Connection
/var/adm/messages (scanned at Tue May 8 08:41:12 AST 2007)
May 8 08:36:22 mx-jes-11 fp: [ID 517869 kern.info] NOTICE: fp(0): PLOGI to 11400 failed state=Packet Transport error, reason=No Connection
/var/adm/messages (scanned at Tue May 8 08:46:12 AST 2007)
May 8 08:42:38 mx-jes-11 fctl: [ID 517869 kern.warning] WARNING: fp(0)::GPN_ID for D_ID=11400 failed
May 8 08:42:38 mx-jes-11 fctl: [ID 517869 kern.warning] WARNING: fp(0)::N_x Port with D_ID=11400, PWWN=10000000c94b138c disappeared from fabric
May 8 08:44:33 mx-jes-11 fctl: [ID 517869 kern.warning] WARNING: fp(0)::N_x Port with D_ID=11400, PWWN=10000000c94b138c reappeared in fabric
May 8 08:44:33 mx-jes-11 fctl: [ID 517869 kern.warning] WARNING: fp(0)::PLOGI to 11400 failed. state=e reason=5.
May 8 08:44:33 mx-jes-11 scsi: [ID 243001 kern.warning] WARNING: /pci@8,700000/QLGC,qla@5/fp@0,0 (fcp0):
/var/adm/messages (scanned at Tue May 8 08:41:12 AST 2007)
May 8 08:36:22 mx-jes-11 fctl: [ID 517869 kern.warning] WARNING: fp(0)::N_x Port with D_ID=11400, PWWN=10000000c94b138c reappeared in fabric
May 8 08:36:22 mx-jes-11 fctl: [ID 517869 kern.warning] WARNING: fp(0)::PLOGI to 11400 failed. state=e reason=5.
May 8 08:36:22 mx-jes-11 scsi: [ID 243001 kern.warning] WARNING: /pci@8,700000/QLGC,qla@5/fp@0,0 (fcp0):

Emmalleres wrote:
you need to download patch 119130-17 for Solaris 10(SPARC) or another patch for Solaris 9 and intel platform.
this will resovle the issue.
[email protected] thread was originally posted more than two years ago. The O.P. has never returned to update the thread though they have been active in the forums since that time (click their username).
The suggested patch would be of value only if the system was installed with Solaris 10 Update 2 or older and had never been patched. Rev-17 of patch 119130 is/was from 2006, which can be seen by reading the README for it.
119130-19 was from May 2006
[http://sunsolve.sun.com/search/document.do?assetkey=1-21-119130-19-1|http://sunsolve.sun.com/search/document.do?assetkey=1-21-119130-19-1]
119130-16 was from Feb 2006
The only information was the excerpt provided in the initial post. It still appears to have been an issue with the storage peripheral.

Warnings in FileReference - can not find the cause

I'm trying to make a loader of a few photos (use FileReference). I get the warnings, but I do not know the reason for their appearance.
warning: unable to bind to property 'fr' on class 'Object' (class is not an IEventDispatcher)
warning: unable to bind to property 'name' on class 'flash.net::FileReference'
warning: unable to bind to property 'data' on class 'flash.net::FileReference'
warning: unable to bind to property 'fr' on class 'Object' (class is not an IEventDispatcher)
warning: unable to bind to property 'name' on class 'flash.net::FileReference'
warning: unable to bind to property 'data' on class 'flash.net::FileReference'
CODE:
import mx.events.CollectionEvent;
import flash.net.FileReferenceList;
import mx.collections.ArrayCollection;
[Bindable]
private var photos:ArrayCollection = new ArrayCollection;
private var frList:FileReferenceList = new FileReferenceList;
private function init():void
photos.addEventListener(CollectionEvent.COLLECTION_CHANGE,function():void
startUploadButton.enabled = (photos.length>0);
clearPhotosButton.enabled = (photos.length>0);
frList.addEventListener(Event.SELECT,addPhotos);
private function selectPhotos():void
var fileFilter:FileFilter = new FileFilter("Images jpeg","*.jpg;*.jpeg");
frList.browse([fileFilter]);
private function addPhotos(e:Event):void
for (var i:uint = 0; i < frList.fileList.length; i++)
var elem:Object = new Object;
elem.fr = FileReference(frList.fileList[i]);
elem.fr.load();
elem.fr.addEventListener(Event.COMPLETE,refreshThumb);
photos.addItem(elem);
private function refreshThumb(e:Event):void
photosList.invalidateList();
public function clearPhoto(data:Object):void
photos.removeItemAt(photos.getItemIndex(data));
photosList.invalidateList();
private function startUpload():void
photosProgressContainer.visible = true;
var request:URLRequest = new URLRequest();
request.url = "http://localhost/tempLoader-debug/upload.php";
var fr:FileReference = photos.getItemAt(0).fr;
fr.cancel();
fr.addEventListener(ProgressEvent.PROGRESS,uploadProgress);
fr.addEventListener(DataEvent.UPLOAD_COMPLETE_DATA,uploadComplete);
fr.upload(request);
private function uploadProgress(e:ProgressEvent):void
photosProgress.setProgress(e.bytesLoaded,e.bytesTotal);
private function uploadComplete(e:DataEvent):void
photos.removeItemAt(0);
photosList.invalidateList();
if (photos.length > 0)
startUpload();
else
photosProgressContainer.visible = false;

In my opinion this is the line that is causing you the warning:
<mx:Image source="{data.fr.data}" maxWidth="100" maxHeight="75"
horizontalAlign="center" verticalAlign="middle" />
That means that data should be a custom binable object and fr should be another
custom bindable object.
like
public class BindableData
    public var fr:BindableData2;
public class BindableData2
    public var data:String;
I am not sure though what you are trying to do though, but I assume you try top
load an image from your disk. This link will help you:
view source enabled...
http://www.everythingflex.com/flex3/flexcampItaly/
the blog post ...
http://blog.everythingflex.com/2009/09/08/flexcamp-presentation-filereference-load-part-1- of-3/
C
From: Astraport2012 <[email protected]>
To: Ursica Claudiu <[email protected]>
Sent: Sun, October 3, 2010 3:07:57 PM
Subject: Re: Warnings in FileReference - can not find the cause
I found the solution to the first part of the warning. Only need to modify the
object as ObjectProxy
public var elem:ObjectProxy = new ObjectProxy;
But with the second part is still a problem (warning: unable to bind to property
'name' on class 'flash.net::FileReference'
warning: unable to bind to property 'data' on class 'flash.net::FileReference').
I do not fully describe the problem in the first message. The main application
calls the component and passes it parameters. They cause errors.
It is this component photoThumb.mxml:
<?xml version="1.0" encoding="utf-8"?>
   width="120" height="110"
   backgroundColor="#FFFFFF" backgroundAlpha="0"
   rollOver="{controls.visible=true;}" rollOut="{controls.visible=false;}">
<mx:Image source="@Embed('t1.png')" width="100%" height="100%" alpha="0"
horizontalAlign="center" verticalAlign="middle"/>
<mx:VBox width="100%" height="90" y="5" horizontalAlign="center" >
<mx:Image source="{data.fr.data}" maxWidth="100" maxHeight="75"
horizontalAlign="center" verticalAlign="middle" />
</mx:VBox>
<mx:Label text="{data.fr.name}" width="118" truncateToFit="false" bottom="0"
textAlign="center" />
<mx:VBox id="controls" visible="false" y="65" right="10" horizontalAlign="right"
>
<mx:Button label="X" click="parentDocument.clearPhoto(data)" fontSize="6"
width="30" height="15" />
</mx:VBox>
</mx:Canvas

MultiProvider design CMP Warnings

Hello,
I'm trying to activate a MultiProvider using some infocubes including 0PA_C01 and 0PAOS_C01. When I check some warnings appears, among others:
Check of MultiProvider ZM:
Error messages from point of view of OLAP processor:
CMP problem occurred in characteristic [ZRUTA]Rutas for InfoProvider 0PAOS_C01
CMP problem occurred in characteristic [ZSTOR_LOC]Storage location for InfoProvider 0PAOS_C01
CMP problem occurred in characteristic [ZRUTA]Rutas for InfoProvider 0PA_C01
CMP problem occurred in characteristic [ZSTOR_LOC]Storage location for InfoProvider 0PA_C01
CMP problem occurred in characteristic [ZRUTA]Rutas for InfoProvider Z0PY_C02
as I can see it's because I'm using some characteristics that exists at some infocubes but not in the infocubes that originated warnings listed above. When trying to activate, Multiprovider activation is succesful, but when trying to retrieve info using Query Designer queries any info about involved infocubes is not available.
Has anyone experienced situations like this and what solution worked to fix it? what action(s) should I take into account?
Hope you could help me. Thanks a lot in advance.
Bernardo

Hi,
Our EDWH landscape was on SPS 13 earlier, for sreolving certain other issues SAP suggested us to with SPS 16 Upgrade. Post SPS Upgrade in our development system, when we tried to activate the Multiprovider we have faced this warnings of CMP( Common Multi Provider) mentioning about the Compounding Infoobjects.There has been no change the struture post SPS, but still we received this error messages, when contacted SAP for the same, it suggested to insert the values mentioned by Jose in RSADMIN table, which will convert the errors to warnings.
Even though the struture remained the same post SPS, these warnings are and added feature after SPS 13.
There is no problem after this data insertion in the RSADMIN table.
Regards,
Ganesh Thota.

Lightroom 5.4. Edit options are greyed out. I tried reset warnings already.

Hi,
I just added a bigger harddrive and reinstalled Lightroom 5.4.
Now, 2 of 3 edit options are greyed out.
No access to plug-ins or external editors for original files.(NEF's)
I tried reset warnings already.

Yes, Nikon transfer was used. From a D800, But that was a year ago.
It has been working fine.
Before I upgraded to 5.4 I had this problem.
When I upgraded to a larger harddrive and re-installed 5.4 the access was limited to only "Copy with Lightroom adjustments."
Last night it started working, I had full access!
But, today it won't work on the same image/plug-ins.
the NIK Collection for example.
This effecting ALL RAW files! D100, D90, D3100, D7000, D800.
My Laptop is doing it now, too!!!
I installed DNG Converter 8.4 with No Difference. NO RAW EDITS.
I can't send a NEF to DXO Optics Pro 9, or anything else!

Change material type - any warnings?

A material with very little history exists in the system as a semi-finished item with 1220 valuation class. One purchase order exists that is due in, in two days. No inventory exists. The problem is that the system is not configured to post goods against 1220 valuation class items. So it needs converted to a finished good since the plan is to sell it after it is received from a vendor.
No open orders or other movements exist in the system. Just one new open po that was created today, and could easily be deleted.
So, delete the po then change the material type using MMAM.
Are there any recommendations/warnings someone can offer before this is done?

Hi,
Pre requisites for changing a material types:
1. If you use a material ledger the material ledger must be settled in it.
2.If the old material type did not require you to specify a price control for the material the new material type must not be configured such that it allows only
standard price as price control.
3.If the material is already in stock or reservations exists or purchase orders exists the following conditions must exist.
      1. The stock values of the new material types must be updated in the same
          G/L Account as the stock values of the old material types
     2. Quantities and values of the new material types must be updated exactly as were by the old material types.
Regards,
nandha

Task UWL and Warnings BPM process

Hi,
I have two questions about:
- Created Tasks in the UWL
- Warnings BPM process.
I have created a BPM process with a one human activitie. This human activity assigned to a task with one potential owner. When i start the process and open the portal UWL, two tasks has been generated!?. Both are the same because when i complete the first task and open the second task, i get the message: " Task has been already completed ".
Second question: when i open the created BPM process, the following warnings appears in the problem tab of NWDS:
Some of the data elements from input mapping of "Cancelled"is not initialized before used.
Some of the data elements from input mapping of "Completed"is not initialized before used.
How can i solve this warning?
Kind regards,
Martin Gerritsen

Hi Martin,
Regarding the "double-task". How did you invoke the process? Via web service? Via NWA? Might it be possible that you submitted the request twice (e.g. double-click instead of a single click?) and that's the reason why 2 tasks are apparing? Or does this happen every time when you start the process?
Just a best guess.
Best regards,
Martin
Martin,
The process will be started by a web service. This service is created as a new WSDL in the BPM environment. This service is connected to the start event of the BPM process and contains a few import parameters. After that i called the service from a R/3 system which started the process.
The 2 tasks apparing everytime i start the process...
When i start the process from the process repository (Netweaver Administrator -> Configuration Management -> Processes and tasks), i get the same problem...
The process contains two human activity's. When the first activity is completed and the second human activity start, 2 tasks will be generated (both the same...)

Deploy warnings using a PL/SQL procedure (from a Public Transform Package)

OWB Version: 10.2
I am receiving the following warnings when I attempt to deploy a map that contains a reference to a custom pl/sql procedure that is setup in a public transformation package:
Warning
ORA-06550: line 115, column 32:
PLS-00112: end-of-line in quoted identifier
ORA-06550: line 115, column 9:
PLS-00103: Encountered the symbol "." when expecting one of the following:
:= . ( @ % ; not null range default character
I reviewed the OWB generated code and I discovered the OWB is a adding two double quotes in front of any reference to the package name. For example.....
BEGIN
COMMIT;
sql_stmt := 'ALTER SESSION DISABLE PARALLEL DML';
EXECUTE IMMEDIATE sql_stmt;
IF NOT ""ZZTEST"."INIT_SF_USER_CLAS_St" THEN
* note the "" in front of ZZTEST, which is the package name.
Has anyone else encountered this issue? I can manually correct the generated the code, but it would be overridden every the time the map is deployed. I encounter the same issue if I import a custom pl/sql procedure from the database into OWB using the Metadata Import Wizard and use the imported procedure in a map. However, I can setup an standalone procedure or function as a public transformation and the map deploys successfully. Please advise.
Regards,
Matt

You have to create a job to start your procedure.
Example :
* http://psoug.org/reference/OLD/dbms_job.html
Then create a procedure to start your job, call it from your dashboard and you're done.
Success
Nico

Trying to set up an out of the box SP 2010 approval workflow that doesn't generate warnings or errors

I have a custom list for which I want an approval workflow. There is only going to be one stop for the approval - creating an item is a request to a person for a new code to be created.
If I do not turn on content approval, then I get the message:
The workflow could not set content approval status. Enable content moderation for this list and run the workflow again.
When I turn on content approval, then when the users go to the custom list to create an item, they see this message:
Items on this list require content approval. Your submission will not appear in public views until approved by someone with proper rights.
Surely I am missing something obvious. I just want a standard SP 2010 form without warnings to gather info from the user, then to create a workflow task that sends a person an email that they need to approve or reject the request.
The second message is going to cause questions from the users. The person who has to approve the tasks wants to be able to see what requests are awaiting approval vs approved vs rejected.
Is this something that is not doable in SP 2010?

the "Approval Process" step is designed for manipulating the "Moderation Status" (Content Approval status) of a list item... What you are seeing is DESIGNED behavior.
When Content Approval is enabled, content changes are not made public until they have been approved. The Approval workflow sends the email to a manager, who is supposed to approve or reject the change.
If Content Approval is DISABLED, there is no point to the workflow.
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

I keep getting warnings that my icloud space is almost full, but I have almost 1GB left

I recently upgraded my iPhone 4S to iOS 8, then a couple of days later got an iPhone 6 (obviously with iOS 8), 64GB. I've removed the backups from my old phone, so in my iCloud, it's telling me there's a backup for my iPad of around 800MB and my (new) iPhone of around 3.2GB. All this seems right (it's mostly photos). I am now getting periodic pop-up warnings from iCloud (running on Windows 7 64-bit Pro) that say "iCloud storage almost full". It's showing that I have about 975MB free which while not a lot, is sufficient since each backup should continue to be around the same size.
The thing that's annoying is that I seem to be getting this warning pretty frequently. I haven't timed it, but it seems like these warnings are happening every 10 or 15 minutes. Is there some threshold of free space that I need to maintain to prevent these warnings?
Would deleting my backup and creating a new one help?

In answer to your first question, unfortunately you don't get allocated more iCloud storage as you buy more devices - it is 5GB free per account.
Regarding the pop-up, I too find it annoying but you won't find a resolution to it on these forums - best thing to do is to submit feedback to Apple and hope they improve it.
https://www.apple.com/feedback/

Get rid of the warnings prior to stretching audio in Arrange

Does anyone know how to get rid of the warnings prior to stretching audio in Arrange?
In the demonstration here on Apples own website, workflow is sped up by the fact that you don't have to hit ok twice before the edit is executed. I have tried to disable warnings etc, but it still does it.
http://www.apple.com/logicstudio/logicpro/
Incidently, I clearing popup warnings using the V-Pots on the Mackie Control doesn't work anymore either. Can anyone confirm this?
This appears to be yet another newly introduced controller bug... Don't even get me started on trying to use a Frontier Tranzport with version 8.

No, the inly option is to uncheck 'Warning before processing function by key command', which doesn't change the situation.
Have you actually done this?

How can I write a program that compiles without warnings?

I tried the following with the 1.5 beta-compiler (build 28; I think):
class Y {
     public static final class Pair<X,Y> {
       private X fst;
       private Y snd;
       public Pair(X fst, Y snd) {this.fst=fst; this.snd=snd;}
       public X getFirst() { return fst; }
       public Y getSecond() { return snd; }
       public String toString() { return "("+fst+","+snd+")"; }
public static void main(String... args) {
     Pair[] pairArr = new Pair[10];              // supposed to be an array of Pair<Integer,Integer>
     for (int i=0; i<pairArr.length; i++)
         pairArr[i] = new Pair<Integer,Integer>(i,i);
     for (int i=0; i<pairArr.length; i++) {
         Pair<Integer,Integer> p = pairArr; // unchecked warning
     System.out.println(p);
     Integer first = p.getFirst();
     Integer second = p.getSecond();
// ... more stuff ...
It turns out that I get an unchecked warning when I extract an element from the array of pairs. Okay, that's fine. How can I avoid the warning? I had expected that an explicit cast would help.
Pair<Integer,Integer> p = (Pair<Integer,Integer> )pairArr;
With a cast I'm telling the compiler: "I _know_ what I'm doing; please trust me." But the compiler still issues a warning.
How can I write a warning-free program in this case? The only thing I can think of, is not using the parameterized type Pair in its parameterized form. But it's not the idea of Java Generics that I refrain from using parameterized types. What am I missing?

It turns out that I get an unchecked warning when I
extract an element from the array of pairs. Okay,
that's fine. How can I avoid the warning? I had
expected that an explicit cast would help.
Pair<Integer,Integer> p = (Pair<Integer,Integer>
)pairArr;
With a cast I'm telling the compiler: "I _know_ what
I'm doing; please trust me." But the compiler still
issues a warning. Yes, but at least you were able to change the warning from "unchecked assignment" to "unchecked cast" which is a little shorter ;-)
Seriously , since arrays of generic types are disallowed, there is probably no way to get rid of these warnings - which makes a strong point for eliminating "unchecked" warnings altogether (see the other thread "selectively suppressing compiler warnings")
Cheerio,
Gernot

Database export stops with the following warnings.

Hello,
I am doing a Database Export/Import Activity. My DB is MS SQL server 2000 and SAP R/3 (4.6C SR2 , 4.6D kernel).
When i try to do a DB export with option split STR and EXT files, my export stops abruptly without giving any erorrs but with a whole list of warnings.
My splitting procedure is using SPLITSTR.PL perl script. I am not using the latest java based split.
For your reference i am pasting the whole DBEXPORT.log file.
(sorry its bit large,,, i hope you dont mind ) )
INFO 2008-03-29 14:36:21 CommandFileController SyFileVersionSave:736
    Saving original content of file
    C:\Users\prdadm\Install\DBEXPORT.R3S ...
INFO 2008-03-29 14:36:21 CommandFileController SyFileCopy:676
    Copying source file C:\Users\prdadm\Install\DBEXPORT.R3S to
    target file C:\Users\prdadm\Install\DBEXPORT.R3S.1 ...
INFO 2008-03-29 14:36:21 CommandFileController SyPermissionSet:2207
    Changing permission for file C:\Users\prdadm\Install\DBEXPORT.R3S
    from 777 to 666.
INFO 2008-03-29 14:36:21 Main
    Preparation successfully completed.
INFO 2008-03-29 14:36:23 DBEXPORTINSTANCE_NT_IND DefValForKey_OS:0
    R3Setup found the share 'SAPLOC' on drive E:.
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
    checking host name lookup for 'ELESAPTMP1'
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
    offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
    host 'ELESAPTMP1' has ip address '172.18.101.21'
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
    offical host name for '172.18.101.21' is 'ELESAPTMP1'.
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
    checking host name lookup for 'ELESAPTMP1'
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
    offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
    host 'ELESAPTMP1' has ip address '172.18.101.21'
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
    offical host name for '172.18.101.21' is 'ELESAPTMP1'.
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
    checking host name lookup for 'ELESAPTMP1'
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
    offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
    host 'ELESAPTMP1' has ip address '172.18.101.21'
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
    offical host name for '172.18.101.21' is 'ELESAPTMP1'.
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
    checking host name lookup for 'ELESAPTMP1'
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
    offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
    host 'ELESAPTMP1' has ip address '172.18.101.21'
INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
    offical host name for '172.18.101.21' is 'ELESAPTMP1'.
INFO 2008-03-29 14:37:17 DBEXPSERVER_NT_IND InternalColdKeyCheck:0
    The CD CDEXPORT1 will not be copied.
INFO 2008-03-29 14:37:36 DBEXPORTINSTANCE_NT_IND CheckValueForKey:0
    The installation phase is starting now. Please look in the log
    file for further information about current actions.
INFO 2008-03-29 14:37:36
    Requesting Export Details
INFO 2008-03-29 14:37:36
    Requesting Export Details
INFO 2008-03-29 14:37:36 DBEXPCOMMONDBENV_NT_MSS SyCoprocessCreate:931
    Creating coprocess osql.exe ...
INFO 2008-03-29 14:37:36 DBEXPCOMMONDBENV_NT_MSS SyCoprocessExecute:171
    The process osql.exe puts out:
INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS GetDbVersion:0
    Version String read from MS SQL Server: Microsoft SQL Server
    2000 - 8.00.2039 (Intel X86)      May 3 2005 23:18:38      Copyright
    (c) 1988-2003 Microsoft Corporation      Enterprise Edition on
    Windows NT 5.2 (Build 3790: Service Pack 2)
INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS GetDbVersion:0
    Major Version read from MS SQL Server: 800
INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS GetDbVersion:0
    Minor Version read from MS SQL Server: 2039
INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS SyCoprocessCreate:931
    Creating coprocess osql.exe ...
INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS SyCoprocessExecute:171
    The process osql.exe puts out:
INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS InternalInstallationDo:0
    You have a correctly configured MS SQL Server with charset cp850
    and sortorder bin_cp850!
INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS InternalInstallationDo:0
ooo MSGERR Wrong type of Parameter: area:74, id:1, typeofParam:4, char:d
ooo MSGERR Dump of parameter with valid type:
ooo MSGWAR MsgAreaName:SY_AREA_RI_MSGL, MsgIdName:RI_MSGL_MIN_MAJORVERSION
ooo MSGERR --- SYLOGDATA:ParaNr: 1, Typ:4
ooo MSGERR --- SYLOGDATA:ParaNr: 2, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 3, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 4, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 5, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 6, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 7, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 8, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 9, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr:10, Typ:1, long=0
ooo MSGERR Wrong type of Parameter: area:74, id:1, typeofParam:4, char:d
ooo MSGERR Dump of parameter with valid type:
ooo MSGWAR MsgAreaName:SY_AREA_RI_MSGL, MsgIdName:RI_MSGL_MIN_MAJORVERSION
ooo MSGERR --- SYLOGDATA:ParaNr: 1, Typ:4
ooo MSGERR --- SYLOGDATA:ParaNr: 2, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 3, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 4, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 5, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 6, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 7, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 8, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr: 9, Typ:1, long=0
ooo MSGERR --- SYLOGDATA:ParaNr:10, Typ:1, long=0    Your actual major version of MS SQL Server is
INFO 2008-03-29 14:37:37
    Requesting Export-Specific Parameters
INFO 2008-03-29 14:37:37
    Testing the Database Connect
INFO 2008-03-29 14:37:37 DBDBSLTESTCONNECT_NT_IND InternalInstallationDo:0
    See logfile dev_dbsl for further information.
INFO 2008-03-29 14:37:37 DBEXPSERVER_NT_IND InternalWarmKeyCheck:0
    The CD CDEXPORT1 will not be copied.
INFO 2008-03-29 14:37:37
    Requesting Information on CD-ROMs
INFO 2008-03-29 14:37:37
    Creating the Export Directories
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
    Checking existence of directory F:\EXPORT~2\DB. If it does not
    exist creating it with user NULL_POINTER, group NULL_POINTER and
    permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
    Changing permission for file F:\EXPORT~2\DB from 777 to 7.
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
    Checking existence of directory F:\EXPORT~2\DB\ORA. If it does
    not exist creating it with user NULL_POINTER, group NULL_POINTER
    and permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
    Changing permission for file F:\EXPORT~2\DB\ORA from 777 to 7.
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
    Checking existence of directory F:\EXPORT~2\DB\INF. If it does
    not exist creating it with user NULL_POINTER, group NULL_POINTER
    and permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
    Changing permission for file F:\EXPORT~2\DB\INF from 777 to 7.
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
    Checking existence of directory F:\EXPORT~2\DB\ADA. If it does
    not exist creating it with user NULL_POINTER, group NULL_POINTER
    and permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
    Changing permission for file F:\EXPORT~2\DB\ADA from 777 to 7.
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
    Checking existence of directory F:\EXPORT~2\DB\MSS. If it does
    not exist creating it with user NULL_POINTER, group NULL_POINTER
    and permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
    Changing permission for file F:\EXPORT~2\DB\MSS from 777 to 7.
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
    Checking existence of directory F:\EXPORT~2\DB\DB2. If it does
    not exist creating it with user NULL_POINTER, group NULL_POINTER
    and permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
    Changing permission for file F:\EXPORT~2\DB\DB2 from 777 to 7.
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
    Checking existence of directory F:\EXPORT~2\DB\DB4. If it does
    not exist creating it with user NULL_POINTER, group NULL_POINTER
    and permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
    Changing permission for file F:\EXPORT~2\DB\DB4 from 777 to 7.
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
    Checking existence of directory F:\EXPORT~2\DB\DB6. If it does
    not exist creating it with user NULL_POINTER, group NULL_POINTER
    and permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
    Changing permission for file F:\EXPORT~2\DB\DB6 from 777 to 7.
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
    Checking existence of directory F:\EXPORT~2\DATA. If it does not
    exist creating it with user NULL_POINTER, group NULL_POINTER and
    permission 7 ...
INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
    Changing permission for file F:\EXPORT~2\DATA from 777 to 7.
INFO 2008-03-29 14:37:37
    Creating the R3load Control Files
INFO 2008-03-29 14:37:37 R3LDCTL_NT_IND R3ldctlDo:0
    C:\Users\prdadm\Install\R3LDCTL.EXE -p C:\Users\prdadm\Install
INFO 2008-03-29 14:37:37 R3LDCTL_NT_IND SyCoprocessCreate:931
    Creating coprocess C:\Users\prdadm\Install\R3LDCTL.EXE ...
INFO 2008-03-29 14:37:38 R3LDCTL_NT_IND R3ldctlDo:0
    WARNING: no technical settings for table "A055" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "A056" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "A064" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "A065" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "AABLG" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "AANK" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "AANL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "ALQRFCMON" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "ALQRFCMONA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "ALQRFCMONO" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "ALQRFCMONQ" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "ANAR" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "ANEV" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "ANGA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "ANLH" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "ANLV" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "ANLW" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "ANLX" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "APQD" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "APQI" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "ATAB" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "B015" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "B060" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "BGPROT" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "BKORA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "BKORR" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "BPHIER" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "BSIW" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "BTCEVTJOB" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "BTCJSTAT" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "BTCOPTIONS" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "BTCSED" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "BTCSEV" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "BTCUEV" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "BUXPRA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "BVOR" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CATCU" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CATDB" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CATL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CATM" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CBPL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CCCFINI" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CD0BAS4VI" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CD0BAS5VI" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CD0MC5" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CD0T200TAB" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CD0T210TAB" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CD0TBSH001" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CDCLS" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CE1S001" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CE2S001" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CE3S001" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CE4S_CP_FLAG" in SAP
    data dictionary - defaults used
    WARNING: no technical settings for table "CF003" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CF005" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CFIS" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CHGRP" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CKHT" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CKKS" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CKKT" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CKPP" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CKPS" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CKPT" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CLRK" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CLU4" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CNTLREM" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "COKAA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "COOI_PI" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "COSPP" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CRHH" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CRID" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CRS_BLOCKS" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CRVP" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CSLT" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CSSK" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CVEP1" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CVEP2" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CVER1" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CVER2" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CVER3" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "CVER4" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DD02ALL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DEBI" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DELM" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DLIX" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DOKALTLANG" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DOKCL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DOKID" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DOKSH" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DOKSI" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DOSSH" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DOSSI" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DSYCR" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DSYLI" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DSYLT" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DSYO1" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DSYO2" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DSYO3" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DSYSX" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DVERS" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DVPOOL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "DVPOOLTEXT" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "E070N" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EANQ" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EBSEG" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EBUB" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EDFIL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EDI30C" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EDI40" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EDIDOC" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EDIE5" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EDMAP" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EIPA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EKAN" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EKPB" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EKUB" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EPIDXB" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EPIDXC" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EREF" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EREN" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "ERET" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EST07" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EST0B" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EST0D" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EST0F" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EWUCUSA2" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "EWUCUSAK" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "FEBKEY" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "FINPL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "FINS" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "FINV" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "FLAPP" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "FLEMP" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "FMCFSI" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "FMCOPI" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "FMGEBER" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "FOH01" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "FREF" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GCLIENTS" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GLOO1" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GLOO2" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GLPO1" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GLPO2" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GLPO3" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GLS2CLUS" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GLSO1" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GLSO2" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GLSO3" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GLSP" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GLT0" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GLTO1" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GLTO2" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GLTO3" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GLTP" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GLTPC" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GSBLCA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "GWFEODE" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "HLPNA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "HRARCENQ" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "HRMS_BIW_PPDELTA" in
    SAP data dictionary - defaults used
    WARNING: no technical settings for table "HRPMPROT" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "HRPMSIM" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "HRPY_RGDIR_TEMP" in SAP
    data dictionary - defaults used
    WARNING: no technical settings for table "IMPREDOC" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "INDX" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "INETX" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "INHB" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "IXDIT" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "IXTYP" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "IXTYT" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "JVT1" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "J_1AWITNR" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "J_1BCBTAXPROC" in SAP
    data dictionary - defaults used
    WARNING: no technical settings for table "J_1BITEMTYPES" in SAP
    data dictionary - defaults used
    WARNING: no technical settings for table "K002" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KALK" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KAPE" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KAPOL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KBPOL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KCPOL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KDPOL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KEPOOL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KGPOL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KNAS" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KNB5" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KNC1" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KNC3" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KNMTK" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KNOB" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KNVA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KNVD" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KNVI" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KNVL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KNVS" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KNVT" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KOCLU" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KONAIND" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KOND" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KONR" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KOTD001" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KOTE001" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KOTE002" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KOTE003" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KOTE004" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KOTE005" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KOTG002" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KOTG003" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "KRED" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "LDAN" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "LDKO" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "LFAS" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "LFB5" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "LFC1" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "LFC3" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "LISA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "LISPLF" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MASE" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MAT1" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MBAN" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MBMP" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MBPR" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MBRK" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MCEKS" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MCLIB" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MCLIO" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MCLIP" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MCLIT" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MCVSRFP" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MCY1" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MEIK" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MEIN" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MEKK" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MEOR" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MHNDO" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MHNKA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MKLK" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MKUB" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MLIB" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MODSAP" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MOFF" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MPRP" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MSAK" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MSEGO1" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MSET" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MSOA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MSPOOL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "MSTA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_ADMC" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_ADRC" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_ADRP" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_AKTE" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_CF01" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_CKKA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_CLFN" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_DARL" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_DGMI" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_HORD" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_IBEW" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_IFLM" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_IIMA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_IRLM" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_J1BA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_J1IA" in SAP data
    dictionary - defaults used
    WARNING: no technical settings for table "M_J1IB" in SAP data
    dictionary - defaults used

Hello,
The version of perl is correct.
Anayways i have solved the problem!
there was problem with the DBEXPORT.R3S file. i referred a SAP note for the same.(Installation of 4.6c on windows). In this check the section for post installation activity.
I hope this can be a input for other experts who may face such problem!!!
Regards,
Shridhar!!!!

Is it possible to make the log pop up of errors/warnings appear for longer?

Dear all
The answer to this question may have already been posted but I could not locate it when searching.
I am running SQL Developer 1.5.1 and I have set up the display so that the log is minimised. When I debug or compile any packages the log of error messages/warnings pops up. However this does not stay on screen long enough for me to be able to read it and only 1 in 4 times do I get to the log window quick enough, in order to click on it to keep it open. Is there away of making the log pop up until I minimise it or at least stay on screen for longer, so that I can reach it in time? I estimate it is currently staying on screen for less than 1 second.
I don't want the log to be displayed all the time because it takes up valuable space, which I find useful when writing my code. It gets in the way even more when I am using the SQL statement window/script output window.
Kind regards
Tim

Thank you K. for your reply.
After all these months of using SQL developer. it never registered with me that hovering over the tab brings it up. I must have brought it up before now but I don't remember doing so if I did.
Problem resolved.
Kind regards
Tim

Warnings: deprected

Similar Messages

Maybe you are looking for