Name is restricted

when I cann anyone my name is restricted, so therefore, nobody is answering because they do not know who the caller is

ddepriest,
We want your friends and family to know it is you calling and not a restricted caller. Let's investigate into this. When did this issue begin? Did you change anything on your phone around the time this began? Please make sure your Caller ID is not blocked. Follow the steps here http://vz.to/1ziEgOU under option 3 under header "Blocking Calls"
LindseyT_VZW
Follow us on Twitter @VZWSupport

Similar Messages

Display technical names of restricted key figures

Hi everybody,
In a query, I would like to display the technical names of restricted key figures instead of their description as a heading. Is that possible and how can I do this?
Thank you for any help, regards, Kathrin!

Hi Kathrin,
I believe you can do this in only one query.In the query you want to have the technical name ..Rigth click>properties> description will change the name of the field only in that specific query..not for all the queries..
Else you can run the query and make changes in workbook format..Even this should serve the purpose..
Ashish.

Model name length restrictions

Using trial and error with the Oracle-Jena adaptor, I seem to have discovered an upper limit of 25 characters on the length of RDF model names that Oracle will let you create. Can somebody verify this for me? If so, I'm curious as to why 25 was chosen. Is that an arbitrary length chosen in the Java code, or is it a restriction imposed by the database itself? Is that length hard-coded, or is it configurable in any way?

It is imposed by the database. It is not configurable. Database has a limit of 30 bytes. Internally, we need to use a few bytes ourselves (as suffix etc). So you are seeing 25.
Thanks,
Zhe Wu

Host Name Character Restriction

Hi Guys,
Is there any way to over come the 13 character specific as the max num of characters allowed in the host name while installing NW
I am trying to install NW2004s.
But my system is having a host name which includes the domain name and obviously goes beyond 13 characters.
Anyway to overcome this.
Thanks in advance
Helpful anwsers will be awarded.

Hi Rosin,
Generally it will look like this:
Computer Name: <name> (max 13 chars)
Domain <domain>
Full computer name: <name>.<domain>
Why your host name includes the domain name?
Also make sure that your computer name (host name) contains alpha-numeric chars.
Omri

How to restrict the length of the input?

Hi all, could any one tell me how to restrict the length of the input string? My SOA Suite is 10.1.3.1
I tried the following; getting an error.
<element name="RestrictLengthProcessRequest">
<simpleType name="SSN">
<restriction base="string">
<length value="10"/>
</restriction>
</simpleType>
where RestrictLengthProcessRequest is the message name of the corresponding .wsdl and SSN is the input whose length is to be restricted.
The error is : 'Attribute name not defined on element simpleType'
Thanks in advance.
Edited by: user11275112 on Aug 27, 2009 11:44 PM

Hi swathi,
For this you have to create a simple data type. No need of writing a code.
Go to Dictionaries -> Local Dictionary -> Data Type - > Simple Type - > Right click and "Create Simple Type".
Here you should create a Simple type with String as built-in Type. Here you will also see the Length Constraints option.
Set the value of maximum length and minimum length. In your case set the value of maximum length to 10. At runtime this will not allow the user to enter more than 10 characters.
Now create an attribute and bind it to this newly created simple type. Bind the value of the input field with this particular attribute.
Regards
Manohar

Validation againt schema using xsd restrictions

Hi, wonder if someone could give me some advice...
I've got an attribute which is of the following type:
<xsd:simpleType name="applicationType">
 <xsd:restriction base="xsd:NMTOKEN">
 <xsd:enumeration value="UKAPP1"/>
 <xsd:enumeration value="UKAPP2"/>
 <xsd:enumeration value="UKAPP3"/>
 <xsd:enumeration value="UKAPP4"/>
 </xsd:restriction>
if I validate this using the validate task in OSB message flow, it passes whatever value I put in the attribute.
If I validate my xml document using XMLSpy, it fails as I haven't entered a valid value. Missing elements etc from my xml will validate perfectly, but not these.
Am I missing something?
Pete

Hi Pete,
Good to hear from you.
I've tried this on the latest version of OSB and it seems to work with the following simple schema:
<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.example.org/NewXMLSchema"
 xmlns:tns="http://www.example.org/NewXMLSchema" elementFormDefault="qualified">
<element name="NewElement">
 <complexType>
 <sequence>
 <element name="payload" type="string"></element>
 </sequence>
 <attribute name="attr" type="tns:attrType"></attribute>
 </complexType>
</element>
<simpleType name="attrType">
 <restriction base="NMTOKEN">
 <enumeration value="UKAPP1"/>
 <enumeration value="UKAPP2"/>
 <enumeration value="UKAPP3"/>
 <enumeration value="UKAPP4"/>
 </restriction>
</simpleType>
</schema>
and a validate action configured as follows:
XPath: ./new:NewElement/@attr
In Variable: body
Against Resource: MCP/SimpleSchema (Type = attrType)
Raise Error radio button checked.
If I send in a message of the form:
<new:NewElement attr="UKAPP3" xmlns:new="http://www.example.org/NewXMLSchema">
<new:payload>string</new:payload>
</new:NewElement>
it validates OK, whereas if I send in a message of the form:
<new:NewElement attr="UKAPP5" xmlns:new="http://www.example.org/NewXMLSchema">
<new:payload>string</new:payload>
</new:NewElement>
validation fails.
If you are still seeing issues with this, can you send me the OSB config to take a look at.

Restrict the value choice of a attribut in xml schema

how can i restrict an attribute value to a list of value, instead of one value by "fixed" key word? something like "option" key word in html?
thanks

Specify the type of the atribute as a SimpleType, which is an enumeration.
<xs:attribute name="attr1" type="attr1Type"/>
<simpleType name='attr1Type'>
 <restriction base='string'>
 <enumeration value='value1'>
 </enumeration>
 <enumeration value='value2'>
 </enumeration>
 <enumeration value='value3'>
 </enumeration>
 </restriction>
</simpleType>

Designer generating CG_REF_CODES inserts without the table name.

We have upgraded our repository from 9i to 10g and now when we generate DDL we get our insert statements for the CG_REF_CODES table without a table name. I am sure that this must be a setting somewhere but I can't find any reference to it in the help. The following is an example of the generated .avt file from our 10g installation.
Thanks in advance,
Chris S.
DELETE FROM
WHERE RV_DOMAIN = 'DURATION_VALUE'
INSERT INTO (RV_DOMAIN, RV_LOW_VALUE, RV_HIGH_VALUE, RV_ABBREVIATION, RV_MEANING)
VALUES ('DURATION_VALUE', 'D', NULL, 'Days', 'Days')
INSERT INTO (RV_DOMAIN, RV_LOW_VALUE, RV_HIGH_VALUE, RV_ABBREVIATION, RV_MEANING)
VALUES ('DURATION_VALUE', 'M', NULL, 'Months', 'Months')
INSERT INTO (RV_DOMAIN, RV_LOW_VALUE, RV_HIGH_VALUE, RV_ABBREVIATION, RV_MEANING)
VALUES ('DURATION_VALUE', 'Y', NULL, 'Years', 'Years')
INSERT INTO (RV_DOMAIN, RV_LOW_VALUE, RV_HIGH_VALUE, RV_ABBREVIATION, RV_MEANING)
VALUES ('DURATION_VALUE', 'B', NULL, 'Business Days', 'Business Days')
INSERT INTO (RV_DOMAIN, RV_LOW_VALUE, RV_HIGH_VALUE, RV_ABBREVIATION, RV_MEANING)
VALUES ('DURATION_VALUE', 'I', NULL, 'Indefinite', 'Indefinite')
COMMIT
/

Sounds like a bug to me, but one thing you can check is the generator options that affect the reference code table. In the Design Editor select your application in the navigator, then the Options menu. Select "Generator Options...", then "General..."
One thing you might fool with is the File Name Length restriction - mine is blank, but then I tend not to use CG_REF_CODES, so I haven't generated them for quite a while. Try setting it to 30, which would be the right number for Oracle, or to 0, which is supposed to mean "no restriction".

How do i get a network name? HOSTNAME=... doesn't work anymore

Hi,
I'm sure this question sounds very n00by, but this used to be working just fine in archlinux by setting the hostname variable and that was the network name as well. No issue and worked like a charme. However, i reinstalled my system and i got the (unpleasant) surprise of a lot of changes.
So, what's the "new" equivalent of HOSTNAME="pc-name" so that it works on the network again? I'm using just the default stock network stuff but with a static ip, no special things.
Right now i do have my hostname set in rc.conf but i can't ping my machine by that name. No, nothing in the local network changed. It really is only a reinstall of a local machine.
Cheers,
Mark

2ManyDogs wrote:
Do you also have the hostname set in /etc/hostname and /etc/hosts?
ArchWiki wrote:
A host name is a unique name created to identify a machine on a network. With Arch Linux, a machine's host name is set in /etc/hostname or until a restart using the hostname command. Host names are restricted to alphanumeric characters. The hyphen (-) can be used, but a host name cannot start or end with it. Length is restricted to 63 characters.
Simply put your host name in to /etc/hostname (archlinux is the host name in this example):
archlinux
After setting a host name, it is also important to include the same host name in /etc/hosts. This will help processes that refer to the computer by its host name to find its IP address, as well as programs that rely on the gethostname() system call to determine the system's host name.
Edit /etc/hosts and add the same HOSTNAME you entered in /etc/hostname:
127.0.0.1 archlinux.domain.org localhost.localdomain localhost archlinux
And do you have a nameserver in /etc/resolv.conf?
If none of this works, can you try using dhcp in your rc.conf just to make sure it's a config problem?
https://wiki.archlinux.org/index.php/HO … e_hostname
Hi,
I tried your suggestions and using dhcp it works partly.
This is my static config:
interface=eth0
address=192.168.1.99
netmask=255.255.255.0
broadcast=192.168.1.255
gateway=192.168.1.2
When i use dhcp (so comment out the lines except interface=eth0) then i do get the name assigned, but i can't ping the pc or access it by name. I can by ip.
If you have more suggestions, please do share
Cheers,
Mark

Creating restricted Key Fig: characteristic Not availlable for selection

Hi,
I am creating a restricted key figure and some of the restricions values are not available fr selections. When I try to type the missing options it only enter them as the first 2 characters.
In one case it basically gives a message that it is not in the master data and but that it will allow for selectinons but I needed to go to the master data to make entries.
What could be going on here?
Thanks

hi Amanda,
would make sense if you want to restrict with the values that exist in infoprovider only or from all master data (if exist in master data and not in infoprovider, no data come when reporting), if you restrict with value not exist in infoprovider then no data will be displayed.
first 2 character .. your characteristic may have length 2 only, it's key, try to right click 'technical names'.
when restrict, you can click 'display other values' button (yellow right arrow),
then there's option to restrict only infoprovider.
however, of course we are allowed restrict with values that not exist,
data in bw development/quality may differ from production,
we may want to restrict values that exist in production but not in dev/QA,
and we need to transport the query from dev to QA/prod.
hope this helps.

Restricting access using groups pulled from OID Authenticator

Using the OID Authenticator provider, can access to WLS be limited to those ldap registered users who belong to a specific group (as specified in ldap) ?
I have setup an oid authenticator provider which works in terms of WLS authentication. By looking in AdminServer.log I can see that a users group is picked up however, I'd like to use the group name to restrict access. Is this possible if specif param's in the oid authenticator are used ?

Remove or replace the ACI that says "Anonymous access" with something more in line with the level of access desired

Domain names with iWeb

I know there has been a lot of discussion on this topic, but I haven't seen anything that answers my more basic questions. I have a .Mac site and would like to give it a personal domain name. I am handy with my .Mac site but know nothing about web pages, domain names etc and how they function (thus the beauty of .Mac that does the work for me). Any help with the following questions would be greatly appreciated. Please keep responses somewhat simple so I can start to understand...
1- If I register a domain name and forward it to my .mac site, what exactly is happening. For example, if I get a name from xyz.com that offers me a domain name, web space, email etc, and I use this name for my .mac site, is anything actually hosted by the xyz.com site? Make sense? All I want is the name. I don't plan to use any of the other services so I want to buy the smallest package. If this package only offers 75 MB of storage, but my .Mac site has more than that on it currently, will this cause a problem? Or, am I just simply slapping on the name and continuing to use all the .Mac functions regardless of the domain name's restrictions. Hope I was clear...
2- Where should I get my domain name? GoDaddy, A Small Orange....?
I guess that is it for now. I really want to know if I will need to change the way I do things, manage storage etc if I get a personal domain name, or is it business as usuall with a new name?
Thanks in advance for your help. Nick

Hi Elmeroguero,
If you buy a domain name at GoDaddy say elmeroguero.com for 10$/yr you then will be able to access the site you publish on .mac by entering elmeroguero.com.
EVERYTHING ELSE is business as usual. You publish your website by hitting publish button in iWeb and so on just as you did until now. All your pages are stored on .Mac and so on. The only thing changing is how you can access your website from browser (nevertheless you will also still be able to access your website typing the web.mac.com/username/ address).
Regards,
Cédric
(Difference between WebForward, WebForward with cloaking and CNAME:
-WebForward: after you typed elmeroguero.com in the browser you get forwarded to web.mac.com/username/ and web.mac.com/username/ will display in the browser
-WebForward with Cloaking: after you typed elmeroguero.com in the browser elmeroguero.com will display in the browser and don't change while people browse through your website
-CNAME elmeroguero.com will display instead of web.mac.com/username/ and while browsing through your website it will look like elmeroguero.com/sitename/nameofpagepeoplelookatnow.html)

ECC 6.0 EHP4 upgrade to EHP5 fails in MAIN_NEWBAS/XPRAS_AIMMRG

from SAPehpi.log
CURRENTPHASE MAIN_NEWBAS/XPRAS_AIMMRG
...started at 20110825140601
...begin processing at 20110825140601
..times self: 0.080000/0.150000 usr/sys, children 0.560000/0.450000 usr/sys.
..finished at 20110825140820 with status UNRESOLVED REQUESTS IN BUFFER.
Error message set: 'Unresolved requests in buffer UT1
Check logfiles 'XPRASUPG.ELG' and '/usr/sap/putUT1/EHPI/abap/log/SAPehpi.ECO''
...begin dialogue at 20110825140821
from SAPehpi.ECO
EXECUTING /usr/sap/UT1/SYS/exe/run/tp (/usr/sap/UT1/SYS/exe/run/tp) pf=/usr/sap/putUT1/EHPI/abap/bin/XPRASUPG.TPP put
UT1
This is /usr/sap/UT1/SYS/exe/run/tp version 380.03.36 (release 720, unicode enabled)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
Process with ID 4903 terminated with status 12
from XPRASUPG.ELG
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR702XPRA00000005.UT1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "14071100")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDEXECL""14071100""UT1"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
<end of logs>
I have searched for ST22 logs and i got a syntax error on program CL_PROXY_STYLESHEET_RUNTIME.
Upgrade 702 has added a segment in the DELETE_CLASS of the program above:
delete from sproxxsl
 where class = class and method = <sproxxsl>-method and client = <sproxxsl>-client.
before:
delete from sproxxsl
 where class = class and method.
"client" field is not part of table SPROXXSL. Which is causing the error.
Any idea on how to continue???
The choices now are:
01) * Repeat phase MAIN_NEWBAS/XPRAS_AIMMRG to continue at the point it stopped
02) - Initialize phase MAIN_NEWBAS/XPRAS_AIMMRG to restart it from the beginning
03) - Accept non-severe errors and repeat phase MAIN_NEWBAS/XPRAS_AIMMRG
04) - Exit this program
Edited by: Rainier Sison on Aug 29, 2011 2:21 PM
Edited by: Rainier Sison on Aug 29, 2011 2:22 PM
Edited by: Rainier Sison on Aug 29, 2011 2:23 PM

Well, I did have a similar issue with RDDEXECL during the import of SAPKB71007.
The solution at that time was updating the kernel to the latest support level, that was released a few weeks after the error with a special modification to fix 'our' issue.
Do you think it's possible to change the kernel on the shadow instance at this moment of EHPI execution?
Hope this helps
Best Regards
Francisco
Edit: The OSS note was: 1551400 - ABAP: Session abort when compiling a deep constant
Edited by: Francisco José Martínez Carretero on Aug 29, 2011 4:54 PM

Getting ORA-22805 when trying to load XML file using SQLLDR

I'm trying to learn the basics of XML since we'll be getting XML files in the near future. I'm using one of the sample schemas that comes with XMLSPY. I loaded this schema into an 11g Oracle DB using XMLSPY:
<?xml version="1.0" encoding="UTF-8"?>

<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:ipo="http://www.altova.com/IPO" targetNamespace="http://www.altova.com/IPO" elementFormDefault="unqualified" attributeFormDefault="unqualified">
 <annotation>
 <documentation>
International Purchase order schema for Example.com
Copyright 2000 Example.com. All rights reserved.
</documentation>
 </annotation>
 
 <include schemaLocation="address.xsd"/>
 <element name="purchaseOrder" type="ipo:PurchaseOrderType"/>
 <element name="comment" type="string"/>
 <complexType name="PurchaseOrderType">
 <sequence>
 <element name="shipTo" type="ipo:Address"/>
 <element name="billTo" type="ipo:Address"/>
 <element ref="ipo:comment" minOccurs="0"/>
 <element name="Items" type="ipo:Items"/>
 </sequence>
 <attribute name="orderDate" type="date"/>
 </complexType>
 <complexType name="Items">
 <sequence>
 <element name="item" minOccurs="0" maxOccurs="unbounded">
 <complexType>
 <sequence>
 <element name="productName" type="string"/>
 <element name="quantity">
 <simpleType>
 <restriction base="positiveInteger">
 <maxExclusive value="100"/>
 </restriction>
 </simpleType>
 </element>
 <element name="price" type="decimal"/>
 <element ref="ipo:comment" minOccurs="0"/>
 <element name="shipDate" type="date" minOccurs="0"/>
 </sequence>
 <attribute name="partNum" type="ipo:Sku"/>
 </complexType>
 </element>
 </sequence>
 </complexType>
 <simpleType name="Sku">
 <restriction base="string">
 <pattern value="\d{3}-[A-Z]{2}"/>
 </restriction>
 </simpleType>
</schema>
Then I created an XMLType table:
CREATE TABLE purchaseOrder OF XMLType
XMLSCHEMA "ipo.xsd" ELEMENT "purchaseOrder"
I'm trying to load the sample XML file ipo.xml into purchaseOrder using SQLLDR. This is ipo.xml:
<?xml version="1.0"?>

<ipo:purchaseOrder xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ipo="http://www.altova.com/IPO" orderDate="1999-12-01" xsi:schemaLocation="http://www.altova.com/IPO
ipo.xsd">
 <shipTo export-code="1" xsi:type="ipo:EU-Address">
 <ipo:name>Helen Zoe</ipo:name>
 <ipo:street>47 Eden Street</ipo:street>
 <ipo:city>Cambridge</ipo:city>
 <ipo:postcode>126</ipo:postcode>
 </shipTo>
 <billTo xsi:type="ipo:US-Address">
 <ipo:name>Robert Smith</ipo:name>
 <ipo:street>8 Oak Avenue</ipo:street>
 <ipo:city>Old Town</ipo:city>
 <ipo:state>AK</ipo:state>
 <ipo:zip>95819</ipo:zip>
 </billTo>
 <Items>
 <item partNum="833-AA">
 <productName>Lapis necklace</productName>
 <quantity>2</quantity>
 <price>99.95</price>
 <ipo:comment>Need this for the holidays!</ipo:comment>
 <shipDate>1999-12-05</shipDate>
 </item>
 <item partNum="748-OT">
 <productName>Diamond heart</productName>
 <quantity>1</quantity>
 <price>248.90</price>
 <ipo:comment>Valentine's day packaging.</ipo:comment>
 <shipDate>2000-02-14</shipDate>
 </item>
 <item partNum="783-KL">
 <productName>Uncut diamond</productName>
 <quantity>7</quantity>
 <price>79.90</price>
 <shipDate>2000-01-07</shipDate>
 </item>
 <item partNum="238-KK">
 <productName>Amber ring</productName>
 <quantity>3</quantity>
 <price>89.90</price>
 <ipo:comment>With no inclusions, please.</ipo:comment>
 <shipDate>2000-01-07</shipDate>
 </item>
 <item partNum="229-OB">
 <productName>Pearl necklace</productName>
 <quantity>1</quantity>
 <price>4879.00</price>
 <shipDate>1999-12-05</shipDate>
 </item>
 <item partNum="128-UL">
 <productName>Jade earring</productName>
 <quantity>5</quantity>
 <price>179.90</price>
 <shipDate>2000-02-14</shipDate>
 </item>
 </Items>
</ipo:purchaseOrder>
This is what's in the control file:
LOAD DATA
INFILE *
INTO TABLE purchaseOrder TRUNCATE
xmltype(xmldata)
FIELDS
xmldata LOBFILE (CONSTANT ipo.xml)
BEGINDATA
0
The load fails with:
Record 1: Rejected - Error on table PURCHASEORDER.
ORA-22805: cannot insert NULL object into object tables or nested tables
Another question I have is, how do we know how many records (0's) to specify in the control file? In this case there's only one but when real files are used we won't know how many are in the file.
Thanks for your help!

The concept was "Don't use SQL*Loader to parse XML".
You can use SQL*Loader to load an entire XML document into the DB. That is fine. You can do the same via BFILENAME to read in files from disk as well.
If you want to parse XML, do that from within Oracle via PL/SQL and/or SQL. The solution depends upon your version of Oracle and what is good enough for you in terms of performance.
So the basics are
a) How am I getting the information?
b) How am I getting in into Oracle?
c) How do I want to parse it?
As I see the schema, it only allows for one ipo:purchaseOrder node in the document, since that is the root node. If you have multiple in the incoming file, you no longer have valid XML, both per the schema and because you have no single root node. You have an XML fragment, which must be treated different.
Just trying to understand the question since I now realize it does not agree with what the schema in your initial example shows.

Urgently Upgrade Stop In XPRAS_UPG Phase

Hi all,
This is our infrastructure:
Windows 2000
Oracle 9.2.0.7
SAP 4.6B
Kernel Release 46D
We are upgrading our DEV System to R/3 Enterprise 4.7 Ext. 2 Sr1
Our Upgrade Process Stop in the XPRAS_UPG Phase. Basically it gives this error:
WARNING: tp terminated with status 12
R3up> ERROR: tp terminated with error status -1
R3up> ERROR: 2 errors detected during XPRAS_UPG
R3up> ERROR: 1 activities have been aborted in XPRAS_UPG
R3up> ERROR: Operation(s) not completely processed.
 Remaining change request found in buffer TVD.
 Ignoring aborted import steps will cause severe inconsistencies
Logs that we reviewed:
XPRASUPG.ECO and R3up.ECO
the problem is with the RDDEXECL JOB. Which is in the status CANCELED
When we Check the JOB LOG it gives this:
 22.10.2007 10:59:35 Job started
22.10.2007 10:59:35 Step 001 started (program RDDEXECL, variant , user ID DDIC)
22.10.2007 10:59:35 All DB buffers of application server vensapd were synchronized PU
22.10.2007 11:01:17 ABAP/4 processor: CONVT_CODEPAGE_INIT
22.10.2007 11:01:17 Job cancelled 00
When you click on ABAP/4 processor: CONVT_CODEPAGE_INIT you get this:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17

The conversion of some code pages is not supported.
What happened? 
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
Error analysis
 An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
 'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure "READ_TEXTLINES" "(FORM)".
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the
LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X u00F0####u00CCu00FF#,").
Please Some help!
We saw this note:
122597 Ignoring errors in the phase XPRAS
So we try with the option "u00CFgnore" + "Repair Severe Errors" but nothing happens, in remains in the same place, Start the Phase a again and Stop at the same point.
676135 Short Dump when you import Support Packages
This notes explain this: (Page 3 Paragraph 3)
If you are still upgrading, import the transport order into the system using 'R3trans -i <data file name>'. Enter the correct path to the data file (possibly DIR_PUT).
But we are scared about to STOP the upgrade here (Like 'cancel' option instead of continue and after restart the upgrade) does somebody apply this note?
This are the logs:
XPRASUPG.ECO
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR620ZF1.TVD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "10593502")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDEXECL""10593502""TVD"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
R3up.ECO:
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 15160 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Copying file D:\usr\sap\put\bin\XPRASUPG.TPP to D:\usr\sap\put\bin\AKKU.TMP
Copying file D:\usr\sap\put\buffer\TVD to D:\usr\sap\put\buffer\AFTXPRAS.BUF
Phase XPRAS_UPG:
Deleting file D:\usr\sap\put\log\CONNECT.LOG
R3up> Starting subprocess tp.exe with id 4196 at 20071022101802
EXECUTING D:\usr\sap\TVD\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\XPRASUPG.TPP put TVD
Environment: dbs_ora_schema=SAPR3
Environment: dbs_ora_tnsname=TVD
Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC
Environment: ORACLE_HOME=D:\oracle\TVD\920
Environment: ORACLE_SID=TVD
This is D:\usr\sap\TVD\SYS\exe\run\tp.exe version 340.16.37 (release 640)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
STARTSAP continues...
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 16400 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Copying file D:\usr\sap\put\bin\XPRASUPG.TPP to D:\usr\sap\put\bin\AKKU.TMP
Copying file D:\usr\sap\put\buffer\TVD to D:\usr\sap\put\buffer\AFTXPRAS.BUF
Phase XPRAS_UPG:
Deleting file D:\usr\sap\put\log\CONNECT.LOG
R3up> Starting subprocess tp.exe with id 4196 at 20071022105721
EXECUTING D:\usr\sap\TVD\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\XPRASUPG.TPP put TVD
Environment: dbs_ora_schema=SAPR3
Environment: dbs_ora_tnsname=TVD
Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC
Environment: ORACLE_HOME=D:\oracle\TVD\920
Environment: ORACLE_SID=TVD
This is D:\usr\sap\TVD\SYS\exe\run\tp.exe version 340.16.37 (release 640)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
STARTSAP continues...
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 15096 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Best Regards,
Desiree Cardenas

Hi Eric,
In fact in the previous post you can see:
the problem is with the
RDDEXECL JOB. Which is in the status CANCELED
When we Check the JOB LOG it gives this:
22.10.2007 10:59:35 Job started
22.10.2007 10:59:35 Step 001 started (program RDDEXECL, variant , user ID DDIC)
22.10.2007 10:59:35 All DB buffers of application server vensapd were synchronized PU
22.10.2007 11:01:17 ABAP/4 processor: CONVT_CODEPAGE_INIT
22.10.2007 11:01:17 Job cancelled 00
When you click on ABAP/4 processor: CONVT_CODEPAGE_INIT you get this:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17
The conversion of some code pages is not supported.
What happened?
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure "READ_TEXTLINES" "(FORM)".
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the
LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X ð####Ìÿ#,").
Sorry for the big amount of information. I will put the complete JOB LOG.
LOG:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17
The conversion of some code pages is not supported.
What happened?
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
If the application required you to enter a code page, you may be able to
avoid the error by restarting the application and entering a different
code page.
You can display the available codepages using the transaction SCP. For
more utilities for codepages, use the transaction SNLS.
Error analysis An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure
"READ_TEXTLINES" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X ð####Ìÿ#,").
How to correct the error
The exception must either be prevented, caught within the procedure
"READ_TEXTLINES"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"CONVT_CODEPAGE_INIT" CX_SY_CODEPAGE_CONVERTER_INITC
"SAPLSTXD" or "LSTXDFDB"
"READ_TEXTLINES"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
 To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
 To obtain this, call the system log with Transaction SM21
 and select the "Print" function to print out the relevant
 part.
3. If the programs are your own programs or modified SAP programs,
 supply the source code.
 To do this, you can either use the "PRINT" command in the editor or
 print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
File attributes no file
System environment
SAP Release.............. "620"
Application server....... "vensapd"
Network address.......... "10.55.46.71"
Operating system......... "Windows NT"
Release.................. "5.0"
Hardware type............ "4x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 11
Short dump setting....... "full"
Database server.......... "VENSAPD"
Database type............ "ORACLE"
Database name............ "TVD"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Jun 25 2004 20:55:59"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "21"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Program............. "SAPLSTXD"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "SAPLSTXD" in "READ_TEXTLINES".
The main program was "RDDEXECU ".
The termination occurred in line 82 of the source code of the (Include)
program "LSTXDFDB"
of the source code of program "LSTXDFDB" (when calling the editor 820).
The program "SAPLSTXD" was started as a background job.
Processing was terminated because the exception "CX_SY_CODEPAGE_CONVERTER_INIT"
occurred in the
procedure "READ_TEXTLINES" "(FORM)" but was not handled locally, not declared
in the
RAISING clause of the procedure.
The procedure is in the program "SAPLSTXD ". Its source code starts in line 75
of the (Include) program "LSTXDFDB ".
Best Regards,
Desiree Cardenas

Name is restricted

Similar Messages

Maybe you are looking for