How to handle directories with special characters in their name

I can't figure out how to recode the second clause of this function to handle directories like one named "[]"
function Get-DiskUsage {
# parse and pray (but it does accept directory []
dir |
? { $_.psIsContainer } |
$size = ((@(cmd /c dir /s $_.name)[-2])[25..39] -join '')
if ($size[14] -eq ' ') {
$size = ' ' + ((@(cmd /c dir /s $_.name)[-2])[25..38] -join '')
$name = $_.name
' ' + $size + ' ' + $name
# object oriented, but it does not accept directory []
Get-ChildItem -Directory |
Select-Object @{ Name="Size";
Expression={ ($_ | Get-ChildItem -Recurse |
Measure-Object -Sum Length).Sum + 0 } },
Name

Here is the function with additional functionality to count bytes in the files in the directory itself as well as subdirectories, and accept an optional argument to specify the target directory.  I wish there was a better way
to do this without modifying and later restoring $pwd
function Get-DiskUsage {
# Discovers how much space is allocated in the directories at and below
# the current directory
# Inspired by a version from Windows PowerShell Cookbook by Lee Holmes
# http://www.leeholmes.com/guide
# The change to parse ] and [ correctly in a directory name was created by Rhys W Edwards
# http://social.technet.microsoft.com/Forums/en-US/f4f0a133-8c4d-4089-8047-274dbc03567b
# if there is an argument, then validate it as an actual directory and set $pwd to it
if ($args.length -gt 0) {
if ((Test-Path -Path $args[0] -PathType Container) -eq $False) {
return
$pwdsave = $pwd
cd $args[0]
# count of bytes in the files in the directory itself
(Get-ChildItem | Measure-Object -property length -sum) |
Select-Object @{Name='Size';Expression={$_.Sum}},@{Name='Name';Expression={$pwd}}
# count of bytes in the files in the subdirectories
Get-ChildItem -Directory |
Select-Object @{
Name='Size';
Expression={
( $_ -replace '\[','`[' -replace '\]','`]' |
Get-ChildItem -Recurse |
Measure-Object -Sum Length).Sum + 0 }
},Name
# restore $pwd is needed
if ($args.length -gt 0) {
cd $pwdsave

Similar Messages

  • Tag Query with Special Characters in Tag Name not working

    Hello-
    We are on SAP xMII 12.0 sp8.6, connecting to Honeywell's PHD. We are doing Tag Queries, and all is working well, except when there are special characters in the Tag Name (+, /, \) We have attempted to do the Encoding of the tag name, such as as is returned from the function xmlencodename and also tried URL Encoding.
    Here is our tag which returns nothing.
    82TK1INV.OCTANE_R+M/2
    We have also tried these encoded versions, still to no avail:
    82TK1INV.OCTANE_R%2BM%2F2
    82TK1INV.OCTANER_M_2
    Any help on how to return the values with special characters in the tag name would be very helpful!
    thanks,
    Paul Mazeika

    To Chianti's question of why can't/shouldn't MII work with those bizarre tag names...
    Actually, there are a number of reasons:
    1) It's a poor design practice to use characters like that in tag names, regardless of the underlying system.  That type of information is best assigned to the tag description, not the tag name.  I've even seen idiots put leading spaces on tag names...figure that one out!
    2) MII uses XML extensively, and XML's syntax rules dictate what is and is not acceptable for XML element and attribute names, and many of these special characters are not permitted.
    3) Usage of characters in tags that also represent mathematical operators greatly complicate the parsing and processing of expressions that involve tag names
    In general, it reminds of the story of the guy who walks into the doctor, bangs his fist against a specific spot on his head, and says "Doc, it hurts when I do this", to which the doctor responds, "so don't do that". 
    So, Don't Do That.

  • Renaming files with invalid characters in their names on NTFS partitions, introduced by operating systems other than Windows

    Essentially, Linux created some files with colons (:) in the name on a NTFS partition where I have Windows installed. I have since uninstalled Linux, but now I can only view these files in Windows Explorer. I can't open them, I can't even rename them to
    correct the problem. It's as if they don't exist, because of the invalid search paths.
    If I try to rename them in Windows Explorer I get following message.
    The file name you specified is no valid or too long.
    Specify a different file name.
    Well isnt' that something?... isn't that nice? Windows is able to display these files, but it doesn't allow me to open them and it certainly doesn't like me to rename them. So why is it whining about it then, when I'm trying to help? It says "try a different
    file name". Yeah, right! Like I haven't tried that one already! It doesn't matter what file name I input it will never accept it.
    So what am I supposed to do now? Ditch Windows and go back to Linux? Surely, Microsoft doesn't like the sound of that. Sure, I could reinstall Linux or run a Linux live system to correct the problem. But what good is Windows then? I might as well switch to
    Linux altogether.
    After doing some research I now know by fact that it's (kind of) possible to rename files from UNIX and UNIX-like operating systems to those compliant with Windows by using something called file name character translation. To some level this is essential and
    necessary for Windows interoperability with other operating systems (Windows is not the only operating system in the world). But this seems to be very complicated and I can't get my head around it. My brain is in overload. I don't know where to start.
    Once there was a...
    There's the Windows Services for UNIX (SFU) 1.0, 2.0, 3.0, 3.5. The first two versions were based on MKS Toolkit, a package licensed by Microsoft from MKS Inc. The later versions were based on the similar Interix product, after Microsoft purchased the company
    that made it.
    Then there's the new Subsystem for UNIX-based Applications (SUA). These are services for UNIX components. They are supposed to have Client for NFS v3 included as well. But the server components from the SFU line is missing (e.g. Server for NFS). These are included
    in Server editions of Windows.
    Then there's the Microsoft Knowledge Base article
    289627: "How to Enable File Name Character Translation". This article seems to describe exactly my situation.
    Windows and UNIX operating systems have restrictions on valid characters that can be used in a file name. The list of illegal characters for each operating system, however, is different. For example, a UNIX file name can use a colon (:), but a Windows
    file name cannot use a colon (:). If a UNIX user attempts to create a file with a Windows illegal character on a Windows Services for UNIX network file system (NFS) share, the attempt is unsuccessful and the UNIX client computer receives an input or output
    error.
    It goes further than that. At first glance, this KB article also seems to offer a solution to this exact problem, with examples as shown below.
    For example, the following maps the UNIX colon (:) to a Windows dash (-):
    0x3a : 0x2d ; replace client : with - on server
    I checked these values in charmap.exe and they are correct. Except for 2D not being a "dash", it's rather a hyphen ("hyphen minus" to be exact), but these two have pretty much the same appearance and they get interchanged a lot, I'm sure
    they are used to it by now. (Yes, the characters! They don't mind.)
    Then there's this registry key.
    HKEY_LOCAL_MACHINE\Software\Microsoft\Server For NFS\CurrentVersion\Mapping
    Well, of course, I don't have Server for NFS. So this is a dead end. Well, actually, it was a dead end from the beginning...
    1. First of all, I'm not working with a network share on a NAS or SAN storage. The files are on the local disk drive where Windows is installed, so that's a DAS for you.
    2. I don't have SFU! Well obviously, I'm on Windows Vista! So that means SUA!
    3. SUA are service components only. No server components. Can you guess what that means? Yeah... no "Server for NFS" since it's a server component.
    4. Windows Vista is a client side operating system! Server for NFS is only offered for use with Windows Server systems.
    5. Back to square one!
    So there you have it. They all lived happy for the rest of their lives...
    I'm stuck here. Can someone tell me what to do? I mean beyond the obvious option to use Linux to fixa a Windows problem? The NTFS file system itself supports colons in file names. It's Windows that doesn't, and so by default it proclaims it invalid character.
    Surely, even a Windows client operating system like Windows Vista should be able to allow the user to at least rename files with invalid characters to something more sensible (from the system point of view) and valid, if not being able to open them as they
    are. Just add some crazy voodoo code to it and it will work. If you can make it possible on Windows Server with UNIX user-mode subsystem on NT kernel, then what's stopping you from giving the Windows client system the same benefit?
    So what now? Purchase a Windows Server 2012 R2 license, copy my invalid files to a NAS share with NFS on a UNIX or Linux system, and have a go at the Windows registry and Server for NFS? Yeah... you're right, it's probably a bit over the top...
    On a second thought... I might as well install Linux again. There are countless situations where Linux has helped me solve problems related to, and more often than not caused by Windows.

    Essentially, Linux created some files with colons (:) in the name on a NTFS partition where I have Windows installed. I have since uninstalled Linux, but now I can only view these files in Windows Explorer. I can't open them, I can't even rename them to
    correct the problem. It's as if they don't exist, because of the invalid search paths.
    If I try to rename them in Windows Explorer I get following message.
    The file name you specified is no valid or too long.
    Specify a different file name.
    Well isnt' that something?... isn't that nice? Windows is able to display these files, but it doesn't allow me to open them and it certainly doesn't like me to rename them. So why is it whining about it then, when I'm trying to help? It says "try a different
    file name". Yeah, right! Like I haven't tried that one already! It doesn't matter what file name I input it will never accept it.
    So what am I supposed to do now? Ditch Windows and go back to Linux? Surely, Microsoft doesn't like the sound of that. Sure, I could reinstall Linux or run a Linux live system to correct the problem. But what good is Windows then? I might as well switch to
    Linux altogether.
    After doing some research I now know by fact that it's (kind of) possible to rename files from UNIX and UNIX-like operating systems to those compliant with Windows by using something called file name character translation. To some level this is essential and
    necessary for Windows interoperability with other operating systems (Windows is not the only operating system in the world). But this seems to be very complicated and I can't get my head around it. My brain is in overload. I don't know where to start.
    Once there was a...
    There's the Windows Services for UNIX (SFU) 1.0, 2.0, 3.0, 3.5. The first two versions were based on MKS Toolkit, a package licensed by Microsoft from MKS Inc. The later versions were based on the similar Interix product, after Microsoft purchased the company
    that made it.
    Then there's the new Subsystem for UNIX-based Applications (SUA). These are services for UNIX components. They are supposed to have Client for NFS v3 included as well. But the server components from the SFU line is missing (e.g. Server for NFS). These are included
    in Server editions of Windows.
    Then there's the Microsoft Knowledge Base article
    289627: "How to Enable File Name Character Translation". This article seems to describe exactly my situation.
    Windows and UNIX operating systems have restrictions on valid characters that can be used in a file name. The list of illegal characters for each operating system, however, is different. For example, a UNIX file name can use a colon (:), but a Windows
    file name cannot use a colon (:). If a UNIX user attempts to create a file with a Windows illegal character on a Windows Services for UNIX network file system (NFS) share, the attempt is unsuccessful and the UNIX client computer receives an input or output
    error.
    It goes further than that. At first glance, this KB article also seems to offer a solution to this exact problem, with examples as shown below.
    For example, the following maps the UNIX colon (:) to a Windows dash (-):
    0x3a : 0x2d ; replace client : with - on server
    I checked these values in charmap.exe and they are correct. Except for 2D not being a "dash", it's rather a hyphen ("hyphen minus" to be exact), but these two have pretty much the same appearance and they get interchanged a lot, I'm sure
    they are used to it by now. (Yes, the characters! They don't mind.)
    Then there's this registry key.
    HKEY_LOCAL_MACHINE\Software\Microsoft\Server For NFS\CurrentVersion\Mapping
    Well, of course, I don't have Server for NFS. So this is a dead end. Well, actually, it was a dead end from the beginning...
    1. First of all, I'm not working with a network share on a NAS or SAN storage. The files are on the local disk drive where Windows is installed, so that's a DAS for you.
    2. I don't have SFU! Well obviously, I'm on Windows Vista! So that means SUA!
    3. SUA are service components only. No server components. Can you guess what that means? Yeah... no "Server for NFS" since it's a server component.
    4. Windows Vista is a client side operating system! Server for NFS is only offered for use with Windows Server systems.
    5. Back to square one!
    So there you have it. They all lived happy for the rest of their lives...
    I'm stuck here. Can someone tell me what to do? I mean beyond the obvious option to use Linux to fixa a Windows problem? The NTFS file system itself supports colons in file names. It's Windows that doesn't, and so by default it proclaims it invalid character.
    Surely, even a Windows client operating system like Windows Vista should be able to allow the user to at least rename files with invalid characters to something more sensible (from the system point of view) and valid, if not being able to open them as they
    are. Just add some crazy voodoo code to it and it will work. If you can make it possible on Windows Server with UNIX user-mode subsystem on NT kernel, then what's stopping you from giving the Windows client system the same benefit?
    So what now? Purchase a Windows Server 2012 R2 license, copy my invalid files to a NAS share with NFS on a UNIX or Linux system, and have a go at the Windows registry and Server for NFS? Yeah... you're right, it's probably a bit over the top...
    On a second thought... I might as well install Linux again. There are countless situations where Linux has helped me solve problems related to, and more often than not caused by Windows.

  • Problem figuring out the encoding for filenames with special characters

    I'm not sure if this is the right forum, but this does seem like an OS issue.
    I brought in a lot of mp3 and m3u files from a Windows machine to my new Mac. Some of the mp3 files have accented characters in their names, and these names appear in the m3u files. But if I add the m3u file to iTunes, it fails to recognize these names and so I lose all the mp3's with special characters in their names.
    I tried to fix this by grabbing the files name in Python, but that didn't work either!
    Here's an example: the file's name is "Voilà l'été.mp3"
    The m3u files says "Voil\xe0 l'\xe9t\xe9.mp3" -- this doesn't work.
    From os.listdir(), I get Voila\xcc\x80 l'e\xcc\x81te\xcc\x81.mp3", but sticking it in an m3u files doesn't work either. (Note that here the characters are encoded as unaccented letter + two byte code for the accent).
    When I try these strings from python, e.g. doing os.stat(), they both work; but iTunes doesn't understand any of them!
    I'd appreciate any hints on how to enter these names in the m3u file so that iTunes can read it. Thanks!

    I know nothing about "m3u" files and how iTunes interprets the file names in them, but if it is not a relative/absolute path problem, then how about just putting the raw file names (not the ones with backslash escape) in m3u file? For example, just put
    Voilà l'été.mp3
    in m3u?
    As for Unicode encoding, HFS+ file system uses the "decomposed form" for accented characters. This means, as you write, à is hex "61 cc 80" in UTF-8, i.e., "a + COMBINING GRAVE ACCENT". The pre-composed form is hex "c3 a0". But my experience is that in most cases both pre-composed and decomosed forms work at the user level (not at the lowest file system level).

  • Sorting of contacts with foreign characters in the name

    Hello,
    I have a large address book, some with Japanese characters in their name.
    I'm on English Language setting for the OS on my iphone and ipad.
    All the contacts with Japanese characters in their name seem to get pushed to the # section of the alphabet rather than at the equivalent roman alphabet letter.
    Also note that adding the Japanese name in the secondary fields of "phonetic first" and "phonetic second" of an existing Roman English based contact sends this to the # section.
    This is poor sorting of contacts. 
    Very poor....

    After posting this I found a solution.  I hadn't tried it this way round.
    https://discussions.apple.com/message/7589528#7589528
    Go into one of your Japanese contacts and click edit.
    Go right to the bottom of the edit page and add field, add phonetic first name, then repeat the step to add phonetic last name.
    Now edit the name of your contact, keep their name in Japanese and enter the phonetic spelling in English.
    Smashin....  :-)

  • FTP-Adapder - Password with special characters

    Hi,
    I hope anybody can help me.
    I have configuriered a sender FTP-Adapter, for login we have a Password with special characters like § or $.
    in the Monitoring now we get this error: 'com.sap.aii.adapter.file.ftp.FTPEx: 530 User cannot log in.'
    if I use a password without the special character, I can Connect to the FTP-Server.
    How can I configure the XI(7.00) to use a password with this characters.
    Thanks for your help
    Mario Grießer

    Hi Mario,
    Check the below thread which might through a light on your issue:
    Re: brbackup using ftp
    Thanks,

  • Problems with special characters like "u00F6" "u00E4" "u00FC"

    Hi,
    we currently face some major problems with special characters like "ö" "ä" "ü". First I thought it is a SP02 specific problem but it still doesn't work with SP03.
    When I start an import the import manager shows correct converted value. "ö"s "ä"s "ü"s are displayed correctly. But after I've done the import I look into the Data manager and I see instead of these characters charcaters like "̈". (note: the character should show a little square box - but the forum cannot desplay it)
    How can I solve this problem?
    Regards
    Nico

    Hi Nico
      Just try it out the following steps, hope it solves ur issue.
    <b>To set one or more values back to their original values:</b>
    1. In the Import Manager Source Values grid, select the values that you want to set back to their original values.
    2. Right-click on one of the values and choose Set to Original Value from the context menu, or choose Values > Apply Value Conversion Filter > Set to Original Value from the main menu.
    3. MDME sets each value back to its original value, which appears in black in the Source Values grid.
    <b>NOTE : You can use the Set to Original Value filter only at the value-level and not at the field level.</b>
    thanks
    Alexander

  • Problems with special characters in InputStream or XPath

    Hello everyone,
    I am having problems with special characters such as ", ', - and so on, everything becomes ? (questionmark). (Not with special nordic characthers (å,æ,ø) though.)
    The encoding of the XML is UTF-8, and the server that holds the webservice is setting encoding to UTF-8 also, so no conflict there.
    What I have done is something like this:
    {code}
    String url = "http://www.formula1.com/rss/news/latest.rss"; // This is not the feed I use, it is a custom XML document
    InputSource is = new InputSource(url);
    DocumentBuilderFactory fct = DocumentBuilderFactory.newInstance();
    DocumentBuilder builder = fct.newDocumentBuilder();
    Document doc = builder.parse(is);
    Element rootElement = doc.getDocumentElement();
    XPathFactory factory = XPathFactory.newInstance();
    XPath xPath = factory.newXPath();
    out.print(xPath.evaluate("/rss/channel/title", rootElement)); // The xml is not a RSS feed, this is just an example.
    {code}
    Please let me know what I am doing wrong, or give me a hint of how to solve this in another way.
    Best regards,
    G.Hansen
    Edited by: G.Hansen on Mar 24, 2009 2:39 AM

    Hello, thanks for you reply. I had to rewrite your code a little, and I think that your code would not really compile, if you tried yourself :-)
    I ended up with something like this:
    our environment is running in 1.4 mode, so I could not use the for-each loop :-(
    public String printEntities(String s) {
         char[] sArray = s.toCharArray();
         StringBuffer sb = new StringBuffer();
           for (int i = 0; i < sArray.length; i++) {
             if (sArray[i] > 256)
                  sb.append("&#x" + Integer.toHexString(sArray) + ";");
         } else
              sb.append(sArray[i]);
         return sb.toString();

  • SSID with special characters showing up in place of the letters

    On a Win 7 machine the SSID list of available wireless networks is showing up with special characters in place of the normal letters in the name of the SSID... It has nothing to do with the Linksys Router, it is a problem on this computer. It makes it impossible to connect to a wireless network. I removed the device and reinstalled it hoping that might help. I can't find any viruses, (Known Viruses) Has anyone here seen this before? I am atttaching a photo of this. Any help appreciated.

    marke1102 wrote:
    On a Win 7 machine the SSID list of available wireless networks is showing up with special characters in place of the normal letters in the name of the SSID... It has nothing to do with the Linksys Router, it is a problem on this computer. It makes it impossible to connect to a wireless network. I removed the device and reinstalled it hoping that might help. I can't find any viruses, (Known Viruses) Has anyone here seen this before? I am atttaching a photo of this. Any help appreciated.
    Is this the only computer having a problem? How many wireless devices are connected and working to the router right now?

  • Problem with special characteres

    Hi. I have a problem with java. I�m making an application that works with special characters and displays correctly on my local machine, as I use escape characters such as &igrave; for �. The problem is when I deploy the application on a unix machine. All of the special characters (�, �, �, etc) appear like a �?� (question mark). Any tips, please?
    Thanks in advance

    Andy2008 wrote:
    Hi. I have a problem with java. I&#146;m making an application that works with special characters and displays correctly on my local machine, as I use escape characters such as &igrave; for �. The problem is when I deploy the application on a unix machine. All of the special characters (&#145;, �, �, etc) appear like a &#147;?&#148; (question mark). Any tips, please?First step: read [this excellent introduction into Unicode|http://www.joelonsoftware.com/articles/Unicode.html], it will give you the basics you need to solve this problem.
    How do you input and output those characters? Simply print them to the console? Or write them to a HTML file (since you mention &<something>; notation)?
    "?" is normally the result when you convert a String (which is always in UTF-16 encoding in Java) to an encoding that can't represent your characters (ASCII for example).

  • Empty datafile with special characters in name

    Hello all
    I'm having an issue with an empty datafile that is in recover mode.
    Previously the following has been successful :
    alter database create datafile 'fully_qualified_file_name' as 'fully_qualified_file_name' ;
    recover datafile 'fully_qualified_file_name' ;
    alter database datafile 'fully_qualified_file_name' online;
    However this time it doesnt work as I get errors :
    ORA-01516: nonexistent log file, data file, or temporary file
    Using the file id doesnt work either.
    When I created a control file trace I can see the datafile has special characters in the name :
    '/oracle/PRD/112_64/dbs/PSPR3I ^?;^?'
    As it is empty, would it be possible to create anothr empty datafile
    using :
    alter database create datafile '/oracle/PRD/112_64/dbs/PSPR3I ^?;^?'
    as '/oracle/PRD/spdata2/r3i_8/r3i.data8';
    then recover datafile 'fully_qualified_file_name' ;
    alter database datafile 'fully_qualified_file_name' online;
    How do oracle commands cope with special characters?
    Thanks for your advice

    user6737818 wrote:
    Hello all
    I'm having an issue with an empty datafile that is in recover mode.
    Previously the following has been successful :
    alter database create datafile 'fully_qualified_file_name' as 'fully_qualified_file_name' ;
    recover datafile 'fully_qualified_file_name' ;
    alter database datafile 'fully_qualified_file_name' online;
    However this time it doesnt work as I get errors :
    ORA-01516: nonexistent log file, data file, or temporary file
    Using the file id doesnt work either.
    When I created a control file trace I can see the datafile has special characters in the name :
    '/oracle/PRD/112_64/dbs/PSPR3I ^?;^?'
    It should work using a file number as the source file definition and a new name for the new file. Works for me:orcl> alter database create datafile 7 as 'c:\tmp\newname.dbf';
    Database altered.
    orcl>

  • Tabular model column rename with special characters - ), *, /, +, %, [ etc

    I am working in tabular model 2012. I have requirement to rename the column names with special characters like ), *, /, +, %, [ etc. When I try to rename in my model, it gives me below error:
    I also tried renaming the columns after creating a new test model with no luck. I may have lived with this error however we have another tabular model which contains special charaters in the name. This makes me believe that there must be some setting that
    I am missing.
    I tried changing the column name in other model having some special characters and it takes it.
    I have gone through this link#
    https://connect.microsoft.com/SQLServer/feedback/details/802009/ssdt-ssas-tabular-column-name-with-special-characters
    and
    http://msdn.microsoft.com/en-us/library/gg492144(v=sql.110).aspx which says that special characters are not allowed in column names however I am able to do it in one of our
    models then why not others.
    Any help is appreciated! Thank you for you time.
    If this post answers your query, please click "Mark As Answer" or "Vote as Helpful".

    Well Mr. Google helped me.. I got the solution:
    Databases of a specific modality and compatibility level can have object names that include reserved characters. Dimension
    attribute, hierarchy, level, measure and KPI object names can include reserved characters, for tabular databases (1103 or higher) that allow the use of extended characters.
    How to change the compatibility, just right click on the .bim file from SSDT and go to properties and change the compatibility to 1103. 
    I hope this will help someone. :-)
    Useful MSDN Links: 
    http://msdn.microsoft.com/en-us/library/bb522632.aspx
    http://msdn.microsoft.com/en-us/library/jj674204.aspx
    If this post answers your query, please click "Mark As Answer" or "Vote as Helpful".

  • How to handle dbms_xmldom with no data values.(no_data_found error in dom)

    hi,
    i have below block,
    DECLARE
    doc dbms_xmldom.DOMDocument;
    node dbms_xmldom.DOMNode;
    elem dbms_xmldom.DOMElement;
    cur_node dbms_xmldom.DOMNode;
    root_elem_data dbms_xmldom.DOMElement;
    root_elem_tab dbms_xmldom.DOMElement;
    root_node_data dbms_xmldom.DOMNode;
    mode_elmn dbms_xmldom.DOMElement;
    mode_node dbms_xmldom.DOMNode;
    mode_text dbms_xmldom.DOMText;
    doc1 DBMS_XMLDOM.DOMDOCUMENT;
    root_node_data1 DBMS_XMLDOM.DOMNODE;
    child_document DBMS_XMLDOM.DOMDOCUMENT;
    child_rootnode DBMS_XMLDOM.DOMNODE;
    V_CLOB CLOB;
    v_doc CLOB;
    v_EMP CLOB;
    v_output_filename VARCHAR2(300) := 'SPOOL_DIR/'||'EMP_XML_FILE.xml';
    l_xmltype XMLTYPE;
    BEGIN
    doc := dbms_xmldom.newDOMDocument;
    node := dbms_xmldom.makeNode(doc);
    dbms_xmldom.setversion(doc, '1.0');
    dbms_xmldom.setCharset(doc, 'UTF8');
    elem := dbms_xmldom.createElement(doc, 'PartnerInfo');
    dbms_xmldom.setAttribute(elem,'xmlns','EMP');
    cur_node := dbms_xmldom.appendChild(node, dbms_xmldom.makeNode(elem));
    mode_elmn := dbms_xmldom.createElement(doc, 'EMPLOYEE');
    mode_node := dbms_xmldom.appendChild(cur_node,dbms_xmldom.makeNode(mode_elmn));
    BEGIN
    SELECT value(e) INTO l_xmltype
    FROM TABLE(XMLSequence(Cursor(SELECT * FROM EMP1 where EMPNO=7501))) e;
    child_document := DBMS_XMLDOM.newDOMDocument(l_xmltype);
    root_node_data1 := dbms_xmldom.importNode(doc,dbms_xmldom.makeNode(dbms_xmldom.getDocumentElement(child_document)),TRUE);
    root_node_data1 := DBMS_XMLDOM.appendChild(root_node_data, root_node_data1);
    EXCEPTION
    WHEN OTHERS THEN
    Dbms_Output.Put_Line('Error in SELECT stmt(UC_PARTNER_MS):::'||'error::'||SQLERRM);
    END;
    dbms_lob.createtemporary(v_doc, true);
    dbms_xmldom.writeToClob(doc,v_doc,'UTF8');
    v_EMP:= v_doc;
    dbms_xmldom.writeToFile(DOC,v_output_filename,'UTF8');
    dbms_xmldom.freeDocument(doc);
    --Dbms_Output.Put_Line('THE OUTPUT IS::'||V_EMP);
    EXCEPTION
    WHEN OTHERS THEN
    Dbms_Output.Put_Line('Error in SELECT stmt(UC_PARTNER_MS):::'||'error::'||SQLERRM);
    END;
    The xml file is 'EMP_XML_FILE.xml'
    <empno>U++kYmcVuGchxbh+++++++++++++++1+</empno>
    <empname>J</empname>
    suppose the empno 7501 is not available in our emp table,
    i got error
    ORA-03113: end-of-file on communication channel
    how to handle xmldom with no data values.
    by
    siva

    hi,
    please give the solution
    by
    siva

  • Adding users with special characters results in error

    Hi all,
    I know it is not best practice to implement a Active Directory with user names containing special characters.
    Unfortunately, we come across some sites that do have these special characters in their user names.
    So, maybe it is a reason to tell the customer to reevaluate their naming policy, but in some cases this is
    just not possible / desirable. What we see when you try to add a user in the Sun VDI portal (1801) with
    a special character in his or her name, the VDI Portal goes back to the main login screen of the portal and
    displays an error:
    Internal Error Occurred!
    You have been logged out because a consistent response could not be guaranteed.
    If the error continues to occur, contact your local technical support and provide .....
    Does anyone know a workaround / fix for this.
    We are running Sun VDI 3.1 Revenue Release.
    Kind regards,
    Sander

    Svanderpost
    Open a support call with Sun there is a fix for this issue.

  • Problems with Special Characters on Exchange Email

    Hello:
    People I have a issue with our Corporate Email on my Iphone. We use Exchange 2003 and we have users with special characters on his emails address.
    I receive fine the email, just appear a errors on the display name. The issue is when I try to reply thie email. A error message popup said:
    Invalid Address
    "email with special characters" does not appear to be a valid email address. Do you want to send it anyway?
    If I press Yes, Iphone try to send the message But I receive another error message:
    Cannot send Mail
    An error ocurred while delivering this message.
    Any Help or Idea?
    Here My Email Configuration
    Email = Email
    Server = Server IP
    Domain = Work Domain Name
    Username = my user id
    Password = my password
    Description = Work
    Use SSL = ON
    S/Mime = Off

    When I Said "we have users with special characters on his emails address" its mean users with ñ,ó, ú, Ñ on his emails address. 
    When I said "just appear a errors on the display name" I mean characters like Âñ¡
    Thanks

Maybe you are looking for