Solaris 9 Extended Attributes

Hi,
I am interested in extended attribute implementation details on TMPFS and NFS file systems.
'fsattr' man contains following:
" Conceptually, the attribute model is fully general. Extended
attributes can be any type of file (doors, links, direc-
tories, and so forth) and can even have their own attributes
(fully recursive). As a result, the attributes associated
with a file could be an arbitrarily deep directory hierarchy
where each attribute could have an equally complex attribute
tree associated with it. Not all implementations are able
to, or want to, support the full model. Implementation are
therefore permitted to reject operations that are not sup-
ported. >>>>For example, the implementation for the UFS file
system allows only regular files as attributes (for example,
no sub-directories) and rejects attempts to place attributes
on attributes.<<<<
Rest of man pages have no information about this feature. I would like to know:
-Is there any kind of limitation on TMPFS or NFS similar to UFS (what can be attribute)?
-What are allowed attribute types on TMPFS or NFS?
-What is point of extended attributes on 'tmpfs'?
-What is maximum number of extended attributes (if exist)?
Does anyone know where to find documentation?

Can you be more specific as to the information you require?
I take it you're interested in the filesystem extended attributes?
A good starting point would be the runat(1) man page but if there's
something specific you're interested in please let me know.
Cheers,
Peter.

Similar Messages

When I restore my Mac with Time Machine and then want to partition my disk, Disk Utility always says incorrect number of extended attributes

When I need to restore my Mac from a time machine backup and then partition my hard disk (the disk inside the computer not the time machine disk), Disk Utility always says "Incorrect Number of Extended Attributes". I then boot into Recovery HD and run disk repair. The result? "The volume Macintosh HD appears to be OK". So then I reboot into normal OS and try the partition again, still Incorrect number of extended attributes. I have even tried /sbin/fsck -fy in single-user mode but it still says the volume is ok. I have tried partition my disk in the recovery HD and it still fails.
Can anyone please help me solve this problem?

Try something stronger, such as DiskWarrior or TechTool Pro.
iMac refurb (27-inch Mid 2011), OS X Mavericks (10.9.4), SL & ML, G4 450 MP w/Leopard, 9.2.2

Cannot create or replace : The specified extended attribute name was invalid.

New problem arrived today. Trying to copy a file from 10.6 server with an XP (SP3) client. I get this error:
Cannot create or replace (file name here): The specified extended attribute name was invalid.
The contents of the file can be copied, but not the folder. Other files can be copied. There are no funny characters. The name is not too long. I propogated the permissions on the share and that had no affect. The problem exists on three different XP systems. Can't find extended properties that could be causeing a problem. Any ideas?

Nikon just released a Firmware update today for the D750

When I check my boot SSD drive using Disk Utility under Mavericks, I often get "Incorrect number of extended attributes" errors. But if I boot off an external drive and check the same SSD, no errors are reported. Is this a bug in Mavericks?

When I check my boot SSD drive using Disk Utility under Mavericks, I often get "Incorrect number of extended attributes" errors. But if I boot off an external drive and check the same SSD, no errors are reported.
This happens not just with the SSD in my Mac Mini, but with another SSD in my MacBook (both now running Mavericks). So far as I know, all of the kit I am using is in good order (despite the file corruption reports). So I am beginning to wonder if it could be due to a bug in Mavericks? Both SSD drives have been formatted to MacOS Extended (journaled) format. Should I have used a different format, I wonder?
Has anyone else encountered this issue?
Does anyone have a solution?
Or an explanation that might help my investigation of the issue?
Thanks guys,

I understand that the Corsair Force 3 is not one of the SSD drives that are supported on Apple Macs.
I did try downloading and using Trim Enabler, but the error message came up both when it was off and when it was on.
I understand that not everyone thinks Trim Enabler is a good program, though there is a new version out now, so I may give it another try.

Can't repair Macintosh HD in Disk Utility (extended attributes)

Hi all,
I have a Retina Macbook Pro with one of them new fancy SSDs in it. I'm running 10.9.3 all up-to-date and am a bit computer-savvy, but I'm more than puzzled by what my Mac has been doing as of late.
When trying to install Windows via Bootcamp, I ran into an error message in the Partitioning step of the process. I hopped into Disk Utility, figuring I could simply partition from there (something in me trusts Disk Utility more than the Boot Camp Assistant). Partition failed!
I then executed the "Verify Disk" command in Disk Utility, only to be told I needed to restart from the Recovery Partition and use the "Repair Disk" function of Disk Utility then. Log of this whole event is at the end of this post, but the offending line seems to be
2014-06-12 20:59:30 -0400: Checking extended attributes file.
2014-06-12 20:59:30 -0400: (It should be 15783744 instead of 14437995)
I then restarted and followed these instructions. "Verify Disk" found no errors, nor did "Repair Disk." I rebooted, only to be met with the same problem!
Is there some sort of lower-level command I can use to repair my disk if I boot in Single User mode or something?
Thanks,
Nathan
2014-06-12 20:58:30 -0400: Disk Utility started.
2014-06-12 20:58:36 -0400: Verifying partition map for “APPLE SSD SD512E Media”
2014-06-12 20:58:36 -0400: Starting verification tool:
2014-06-12 20:58:36 -0400: Checking prerequisites
2014-06-12 20:58:36 -0400: Checking the partition list
2014-06-12 20:58:36 -0400: Checking for an EFI system partition
2014-06-12 20:58:36 -0400: Checking the EFI system partition’s size
2014-06-12 20:58:36 -0400: Checking the EFI system partition’s file system
2014-06-12 20:58:36 -0400: Checking all HFS data partition loader spaces
2014-06-12 20:58:36 -0400: Checking booter partitions
2014-06-12 20:58:36 -0400: Checking booter partition disk0s3
2014-06-12 20:58:36 -0400: Checking file system
2014-06-12 20:58:36 -0400: Checking Journaled HFS Plus volume.
2014-06-12 20:58:36 -0400: Checking extents overflow file.
2014-06-12 20:58:36 -0400: Checking catalog file.
2014-06-12 20:58:36 -0400: Checking multi-linked files.
2014-06-12 20:58:36 -0400: Checking catalog hierarchy.
2014-06-12 20:58:36 -0400: Checking extended attributes file.
2014-06-12 20:58:36 -0400: Checking volume bitmap.
2014-06-12 20:58:36 -0400: Checking volume information.
2014-06-12 20:58:36 -0400: The volume Recovery HD appears to be OK.
2014-06-12 20:58:36 -0400: Checking Core Storage Physical Volume partitions
2014-06-12 20:58:36 -0400: Checking storage system
2014-06-12 20:58:36 -0400: Checking volume
2014-06-12 20:58:36 -0400: disk0s2: Scan for Volume Headers
2014-06-12 20:58:36 -0400: disk0s2: Scan for Disk Labels
2014-06-12 20:58:36 -0400: Logical Volume Group D79A3F82-3153-4DCC-A58F-C9B3ADAD2F6E on 1 device
2014-06-12 20:58:36 -0400: disk0s2: Scan for Metadata Volume
2014-06-12 20:58:36 -0400: Logical Volume Group has a 16 MB Metadata Volume with double redundancy
2014-06-12 20:58:36 -0400: Start scanning metadata for a valid checkpoint
2014-06-12 20:58:36 -0400: Load and verify Segment Headers
2014-06-12 20:58:36 -0400: Load and verify Checkpoint Payload
2014-06-12 20:58:36 -0400: Load and verify Transaction Segment
2014-06-12 20:58:36 -0400: Incorporate 0 newer non-checkpoint transactions
2014-06-12 20:58:36 -0400: Load and verify Virtual Address Table
2014-06-12 20:58:36 -0400: Load and verify Segment Usage Table
2014-06-12 20:58:36 -0400: Load and verify Metadata Superblock
2014-06-12 20:58:36 -0400: Load and verify Logical Volumes B-Trees
2014-06-12 20:58:36 -0400: Logical Volume Group contains 1 Logical Volume
2014-06-12 20:58:36 -0400: Load and verify BDEE2B2F-6770-4707-AE0A-3862965E6414
2014-06-12 20:58:36 -0400: Load and verify B761A88F-B034-44A9-8F54-F7732861C825
2014-06-12 20:58:36 -0400: Load and verify Freespace Summary
2014-06-12 20:58:36 -0400: Load and verify Block Accounting
2014-06-12 20:58:36 -0400: Load and verify Live Virtual Addresses
2014-06-12 20:58:36 -0400: Newest transaction commit checkpoint is valid
2014-06-12 20:58:36 -0400: Load and verify Segment Cleaning
2014-06-12 20:58:36 -0400: The volume D79A3F82-3153-4DCC-A58F-C9B3ADAD2F6E appears to be OK
2014-06-12 20:58:36 -0400: The partition map appears to be OK
2014-06-12 20:58:36 -0400:
2014-06-12 20:58:36 -0400: Verifying volume “Macintosh HD”
2014-06-12 20:58:36 -0400: Starting verification tool:
2014-06-12 20:58:36 -0400: Checking storage system
2014-06-12 20:58:37 -0400: Checking volume
2014-06-12 20:58:37 -0400: disk0s2: Scan for Volume Headers
2014-06-12 20:58:37 -0400: disk0s2: Scan for Disk Labels
2014-06-12 20:58:37 -0400: Logical Volume Group D79A3F82-3153-4DCC-A58F-C9B3ADAD2F6E on 1 device
2014-06-12 20:58:37 -0400: disk0s2: Scan for Metadata Volume
2014-06-12 20:58:37 -0400: Logical Volume Group has a 16 MB Metadata Volume with double redundancy
2014-06-12 20:58:37 -0400: Start scanning metadata for a valid checkpoint
2014-06-12 20:58:37 -0400: Load and verify Segment Headers
2014-06-12 20:58:37 -0400: Load and verify Checkpoint Payload
2014-06-12 20:58:37 -0400: Load and verify Transaction Segment
2014-06-12 20:58:37 -0400: Incorporate 0 newer non-checkpoint transactions
2014-06-12 20:58:37 -0400: Load and verify Virtual Address Table
2014-06-12 20:58:37 -0400: Load and verify Segment Usage Table
2014-06-12 20:58:37 -0400: Load and verify Metadata Superblock
2014-06-12 20:58:37 -0400: Load and verify Logical Volumes B-Trees
2014-06-12 20:58:37 -0400: Logical Volume Group contains 1 Logical Volume
2014-06-12 20:58:37 -0400: Load and verify BDEE2B2F-6770-4707-AE0A-3862965E6414
2014-06-12 20:58:37 -0400: Load and verify B761A88F-B034-44A9-8F54-F7732861C825
2014-06-12 20:58:37 -0400: Load and verify Freespace Summary
2014-06-12 20:58:37 -0400: Load and verify Block Accounting
2014-06-12 20:58:37 -0400: Load and verify Live Virtual Addresses
2014-06-12 20:58:37 -0400: Newest transaction commit checkpoint is valid
2014-06-12 20:58:37 -0400: Load and verify Segment Cleaning
2014-06-12 20:58:37 -0400: The volume D79A3F82-3153-4DCC-A58F-C9B3ADAD2F6E appears to be OK
2014-06-12 20:58:37 -0400: Checking file system
2014-06-12 20:58:37 -0400: Performing live verification.
2014-06-12 20:58:37 -0400: Checking Journaled HFS Plus volume.
2014-06-12 20:58:37 -0400: Checking extents overflow file.
2014-06-12 20:58:37 -0400: Checking catalog file.
2014-06-12 20:58:59 -0400: Checking multi-linked files.
2014-06-12 20:59:30 -0400: Checking extended attributes file.
2014-06-12 20:59:30 -0400: (It should be 15783744 instead of 14437995)
2014-06-12 20:59:30 -0400: Error: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.
2014-06-12 20:59:30 -0400:
2014-06-12 20:59:30 -0400: Disk Utility stopped verifying “Macintosh HD”: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.
2014-06-12 20:59:30 -0400:

I'm having a similar problem with my G4 Desktop.
I have a 2nd internal hard drive and 2 FW Drives.
None of them are able to be verified or repaired using DU.
I get the following message: "Verify volume failed with error Could not unmount disk." And then some message about "make sure that all your files are closed."
I tried soft-booting by holding the shift-key down just as a trouble-shooting idea and I was able to verify and the drives were working well. However, when I restarted in normal mode I was not able to verify or repair.
What is my G4's problem? Why does it need to use that secondary drive in order to operate? What do I need to do to fix it?
Any suggestions?
G4 Dual 1.42 Mac OS X (10.4.6) 1 Gig Ram / 2 Internal Hard Drives

No permission to copy file (to NAS with AFP support) - extended attributes?

For certain files that I copy from one of my drives to the NAS here (Synology 206j), ever since upgrading to Snow Leopard, Finder's behaviour has changed. It will simply refuse to copy the file, stating that "The operation can’t be completed because you don’t have permission to access some of the items."
The source is an external USB drive in Mac OS Extended format, I do have full permissions on the files and in any case the drive is set to ignore ownership.
The target is, like most NASes, in EXT3 format. It's sharing via its own AFP implementation.
I'd have tried repairing permissions, but for whatever reason, it's greyed out on my external drives. Since then I've figured that it was probably not that anyway, which will become apparent:
I tried copying the file via the terminal and it actually worked, but also gave an error: "cp: myfile: could not copy extended attributes to /Volumes/media backup/myfile: Operation not permitted"
This suggests to me that, as expected, the target volume doesn't support extended attributes. But rather than popping up with the message that Leopard did (something along the lines of "your target volume doesn't support extended attributes so your file's metadata may be lost, do you wish to continue") it just aborts instead.
I'm not sure if this is a Snow Leopard problem or a change that Synology need to catch up with. A workaround is to compress the file to ZIP first.
Thought I'd mention it here before trying to report it as a bug somewhere. Anyone else having similar issues, either with a NAS or some other storage, in which case please specify?
Message was edited by: Cloudane

Thanks guys, yeah I've been monitoring the netatalk mailing list myself: they're onto the same problem, have come to the same conclusions about it being Extended Attributes and have much better proof of such than I
It looks like they're currently debating the best way to fix it (pretending to support EAs but sending them to a black hole being the quick and dirty way, but I suspect they'll go for implementation)
It'll be a while for sure, but the Synology guys are very good with Mac support so I'm sure they'll apply the update fairly quickly once the netatalk crew get something public. FWIW, I did detect a certain sense of urgency from the netatalk discussions.
Although it's essentially answered, I'll leave the question marked as unanswered in case Apple come up with a better one
Message was edited by: Cloudane

How to use extends attribute in jsp page directive

Can anybody tell how to extend a existing .jsp file from another .jsp file. I have tried but it gives error.
I have used Extends attribute of page directive as below:
<%@ page extends = "MyAnotherJsp.jsp"%>
I also tried : <%@ page extends = "MyAnotherJsp"%>
I am using Tomcat as a web server
Also tell where to put those files.
Thanks.

Hi I am using Netbeans 5.5, Sun Java System Application Server 9.
ABC.java
package javapackage;
public class ABC{
public String show(){
return "Sandip Gaikwad";
index.jsp
<%@ page extends="javapackage.ABC" %>
<html>
<head>
<title>JSP Page</title>
</head>
<body>
<h1>JSP Page </h1>
</body>
</html>
Above code throws following exception at runtime:-
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP
Generated servlet error:
[javac] F:\Sun\AppServer\domains\domain1\generated\jsp\j2ee-modules\Page_Extends_Attribute_Example\org\apache\jsp\index_jsp.java:36: getPageContext(javax.servlet.Servlet,javax.servlet.ServletRequest,javax.servlet.ServletResponse,java.lang.String,boolean,int,boolean) in javax.servlet.jsp.JspFactory cannot be applied to (org.apache.jsp.index_jsp,javax.servlet.http.HttpServletRequest,javax.servlet.http.HttpServletResponse,,boolean,int,boolean)
[javac] pageContext = _jspxFactory.getPageContext(this, request, response,
[javac] ^
[javac] 1 error
Server log
StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: Unable to compile class for JSP
Generated servlet error:
[javac] F:\Sun\AppServer\domains\domain1\generated\jsp\j2ee-modules\Page_Extends_Attribute_Example\org\apache\jsp\index_jsp.java:36: getPageContext(javax.servlet.Servlet,javax.servlet.ServletRequest,javax.servlet.ServletResponse,java.lang.String,boolean,int,boolean) in javax.servlet.jsp.JspFactory cannot be applied to (org.apache.jsp.index_jsp,javax.servlet.http.HttpServletRequest,javax.servlet.http.HttpServletResponse,<nulltype>,boolean,int,boolean)
[javac] pageContext = _jspxFactory.getPageContext(this, request, response,
[javac] ^
[javac] 1 error
at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:94)
at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:384)
at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:461)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:528)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:507)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:495)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:530)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:412)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:318)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
If I delete the line <%@ extends="javapackage.ABC"%> it works fine. Please tell me what is wrong with this line.

Display non extended attribute in a Custom Report

Hi,
Is it possible to query external attributes (that are not set as extended attributes) in a user report ?
I read in this forum that reports are just meant to query IDM repository, is it still true ?
Thanks,
Ben

Hello Sandra,
Thanks for your reply, but eventhen it fails to load the pdf. Is ADS required to be installed for this?
Can I just pass the pdf_fsize imported from CONVERT_OTF which is of type i.
CALL FUNCTION 'CONVERT_OTF'
    EXPORTING
      FORMAT                = 'PDF'
    IMPORTING
      BIN_FILESIZE          = PDF_FSIZE
bin_file              = pdfxstring
    TABLES
      OTF                   = L_JOB_OUTPUT_INFO-OTFDATA
      LINES                 = LT_PDF
    EXCEPTIONS
      ERR_MAX_LINEWIDTH     = 1
      ERR_FORMAT            = 2
      ERR_CONV_NOT_POSSIBLE = 3
      OTHERS                = 4.
CALL METHOD G_HTML_CONTROL->LOAD_DATA(
     EXPORTING
       TYPE         = 'application' "'text' " 'application'
       SUBTYPE      = 'pdf' "'html' "'pdf'
       size           = PDF_FSIZE
     IMPORTING
       ASSIGNED_URL         = lv_URL
     CHANGING
       DATA_TABLE           = LT_DATA "i_html "LT_DATA
     EXCEPTIONS
       DP_INVALID_PARAMETER = 1
       DP_ERROR_GENERAL     = 2
       CNTL_ERROR           = 3
       OTHERS               = 4 ).
Thanks,
Jaya.

To change the approval limit for Extended attribute PO Value limits

Hi,
We are on SRM 4.0, in PPOMA_BBP for a local purchasing organisation we want to change the approval limit let us say from 100 to 50 but the system is presenting this field as non editable( In stabdard values sub screen)
In Extended attribute tab in organisation structure after selecting the PO Value limits in SRM 4.0 we see two sub screens
a) Standard values
b) Local values
We want to change the approval limit in standard values sub screen from 1000 to 500, which system is presenting as noneditable.
Regrds
Vivek

Hi
Refer these links.
http://help.sap.com/saphelp_srm50/helpdata/en/5a/af5efc85d011d2b42d006094b92d37/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/8b/4fa9585db211d2b404006094b92d37/content.htm
http://help.sap.com/saphelp_srm50/helpdata/en/fa/fa7d3cb7f58910e10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/7f/0fea380bfe6161e10000000a11402f/frameset.htm
Incase it does not helps, pls let me know.
Regards
- Atul

I don't find User Extended attributes in IDM 8

Hi all,
I have installed idm8 and I need to extend the user attributes, but I can't find the User Extended Attributes object (or Extended User Attributes). Can anyone help me?

From the release notes :
Identity Manager 8.0 consolidates the locations where an administrator specifies extended,
queryable, and summary attributes for user objects into the new
IDM Schema Configuration object. (ID-17784) In prior versions of Identity Manager, an administrator
edited the User Extended Attributes configuration object to add extended attributes for
user objects and the UserUIConfig configuration object to specify additional queryable or
summary attributes for user objects. An administrator now edits the IDM Schema Configuration
object for these purposes.

Resource Attributes not saving in Queriable User Extended Attributes

Howdy,
I added a few queriable user extended attributes to IDM. I originally added them in through the configure user attributes interface. I then edited the UserUIConfig to specify that they were queryable. I then edited the User Search Defaults form's getSearchableAttrs function to include these attributes. My added attributes now show up in the search user form, etc., just like I expected them to. Next I configured a new resource adapter for a database table that contained some values I wanted to use to populate these queriable attributes. I wrote a correlation rule, and ran reconciliation on the new resource. It matched up the account entries and automatically matched and linked the account information. So far so good. However, the user extended attributes I defined are not getting populated with the data from the new resource. The mapped resource attributes are treated as part of the user view, but only under the given resource, not as a queriable attribute. I really want to be able to use the find user interface with these datafields. Does anyone know why my data is ot making it into the queriable fields? Do I need to write another rule or workflow? Any advice would be most helpful.
Thanks!
Jim

Queryable attributes refer to attributes stored in the IDM user object, and so need to be referenced as such.
If you want attribute 'foo' in resource 'bar' to be stored as a Queryable attribute, you need to define it like so in your User Form :
<Field name='accounts[Lighthouse].foo'>
    <Expansion>
          <ref>accounts[bar].foo</ref>
    </Expansion>
</Field>This should pull the value from the resource attribute and put it in the IDM attribute. If you refer to it as a global.foo everywhere, that might work (but I find globals to be problematic).
Let me know if it works...
Jason

"Error writing metadata to" message and extended attributes

After being frustrated by this error message in Bridge while trying to apply keywords to various image files I finally took the time to investigate, and I think I found the cause of the issue. In a nutshell, if the extend attribute "com.apple.FinderInfo" has not yet been created for a given file, then this message appears.
The start of the puzzle was that some files would take the keyword and others would not. After observing identical permissions on files that worked and files that did not, I noticed that in a terminal listing of the files in question, some files had extended attributes and some did not (extended attributes are identified by an @ symbol when running ls -la in a terminal window. For example:
-rw-rw-rw-@   1 mike staff 26131946 21 Jan 23:56 120114-133059-4612.cr2
-rw-rw-rw-    1 mike staff      5710 21 Jan 22:42 120114-133059-4612.xmp
-rw-rw-rw-@   1 mike staff 27200794 17 Jan 17:52 120114-133145-4613.cr2
-rw-rw-rw-    1 mike staff      5702 21 Jan 22:42 120114-133145-4613.xmp
-rw-rw-rw-@   1 mike staff 26973498 21 Jan 23:07 120114-133149-4614.cr2
-rw-rw-rw-@   1 mike staff      6648 21 Jan 23:19 120114-133149-4614.xmp
As you can see, the file called 120114-133145-4613.xmp has not extended attribute, but the file 120114-133149-4614.xmp does. The former throws an error when applying a keyword, the latter does not.
So I dug a bit further and it appears that when the file attribute called com.apple.FileInfo is missing from an xmp file, metadata cannot be witten. The contents of this extended attribute for a working XMP file look like this
$ xattr -l 120114-133058-4611.xmp
com.apple.FinderInfo:
00000000 54 45 58 54 43 52 61 77 00 00 00 00 00 00 00 00 |TEXTCRaw........|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000020
According to specs I found googling, the first 4 bits identify the file type (TEXT), and the next four identify the file creator (CRaw). IOW no file-specific info seems to be present.
So as a test, I simply copied the contents of com.apple.FinderInfo from a file that had it to a file that didn't. Once the file that didn't received the new attribute, metadata writes worked. The command I used for the copy was
xattr -wx com.apple.FinderInfo "`xattr -px com.apple.FinderInfo 120114-133534-4633.xmp`" 120114-133041-4602.xmp
It also appears that this metadata is written by Bridge based on some unknown trigger, because occasionally during my investigation a file that previously would not take metadata suddenly did, and once I knew to look for extended attributes, in every case the file in question suddenly had com.apple.FinderInfo extended attribute.
So...I'm not sure if this is a bug in finder or in bridge, but it is definitely a bug and needs to be addressed.
...Mike

I have tried purging the cache, and also deleting it entirely and starting over, to no effect.
Mike
just did a quick try and don't know if it is the right way.
Using Lightroom 3.6 (not very familiar with Lightroom) and Bridge 4.0.5.11 on MacOSX 10.6.8
I randomly choose some CR2 files that where somewhere on my system and copied them to a new folder. Imported them in Lightroom and added some rating and a few keywords. (with setting metadata to XMP file active)
Then went to Bridge and opened the same folder. After caching Bridge showed the info as filed in Lightroom. Added some keywords to all files without problem. Went back to Lightroom (restarted it and had to choose read metadata menu. After this no problem to read new keywords form Bridge. But they only show in Italic because the have not been made persistent in the Bridge keyword list, however this is as expected behavior.
Tried a develop setting and that was also showing in Bridge correctly. Went a few times back and fort (files in Lightroom showing a memo with Exclamation sign top right of the in Bridge changed thumbnail asking for reading metadata).
Is this about the way you mean to describe?
And when having set Automatically export changes to XMP have you set this option in both Lightroom and Bridge (this s to be found in the Camera Raw preferences 'save image settings in: sidecar XMP')
And there are a few things to refresh also in Bridge besides the deleting of the cache file, you can also delete the Bridge plist file from the user library preferences and restart Bridge holding down option key and chose reset preferences. And did you run the check and repair permissions for your system also?
I tried to look in terminal but could not find a way to use the ls -la command on the folder with changed files so no comparing on that side I'm afraid.

HELP: Extended Attributes Not Appearing In Instances of Custom Content Type

From Java code I create a custom content type derived from Document and define some extended attributes with default values for that type. All done using the same methodology shown in the Developer's Guide and Oracle example code.
I start ifsmgr and I can indeed see the content type and the extended attributes.
If I however create an instance of this (custom) type, either from the Viewer (file Upload) or from Java code (using code simuilar to createDocument from the Oracle ContentModule example), the extended attributes do not appear!
BUT, if I delete one of the extended attributes using ifsmgr (highlight one of my extened attributes, click on "Remove", and then "Apply"), from that point on the previously missing extended attributes appear (except for the one I deleted of course) when I create files of the custom type from either Java code or the Viewer. Furthermore, once I get ifs to "see" one of these extended attributes in this manner, I can delete the extended attribute and re-create it from Java at will and it will appear in created instances of my custom content type just fine.
If however I add another new extended attribute to the custom content type, I have to do the "Remove/Apply" drill in ifsmgr to get this new attribute to appear in created files of my custom type.
I've tried deleting all instances of the custom type and closing both ifsmgr and the Viewer, but unless I delete one of the extended attributes from ifsmgr I cannot get new extended attributes to appear.
What do I need to do in my 9ifs Java code to get new custom content extended attributes to appear in instances of that custom type?
Thank you,
Jeff "Did Kafka Write ifs?" Rininger

Dear @user10993347,
As mentioned by @vinod2303, you need to maintain content relationships along with subscriptions.
Regards,
Saurabh

Custom report Extended Attribute

Hi,
On my user selection screen I just need a multiple selection box and user related data needs to be populated in it, can anybody guide me on this.
Thanx

Open BPE --
click File - >
--> OpenRepository Object
---> Forms
--->EndUserMenu
you can have a look at EndUserMenu
if you want to display custom forms then you need
login as configurator to administrator module
Click configure Tab
--->Forms and Process Mapping
you can find EndUserMenu
change the name of the EndUserMenu to your form name(should be uploaded to the IDM)
for adding attributes to your User Object
login to your http:\\localhost:8080\idm\debug pages then select
ListObjects -->configuraton
from the list of values select the User Extended Attributes for edit
then you can add your Extended Attributes here. eg PassportNo
<List>
<String>firstname</String>
<String>PassportNo</String>
</List>
</List>

CSI: update_item_instance issues while creating extended attributes

Hello,
For our customer's data conversion, installed base instances have already been created, there is only need to create extended attributes.
Issues I have encountered are:
- Whenever an error is encountered in the API call, all following records are rejected with the same error (even the same instance ID/primary key/attribute ID) as the first error record.
- Extended attributes are randomly entered in the wrong fields (as if one field had gone missing and the others had been updated)
- Date formats have been changed from DD/MM/YYYY to DD-MON-YYYY when consulting from Installed Base (but this happened only once)
Other information: There are 14 extended attributes to be added for each item instance, I removed some of the attributes to make the code more readable.
I followed the metalink note that shows the implementation method for this API and only added the recursive elements that we needed for the 14 attributes + functions to retrieve item_id and such.
The "message()" function replaces is defined as FND_FILE.PUT_LINE(which =>fnd_file.log,buff => p_msg);
PROCEDURE main (errbuf OUT VARCHAR2
                    ,retcode OUT NUMBER
IS
     vl_status                BOOLEAN;
     vl_item_id                NUMBER;
     vl_instance_id           NUMBER;
     v_count               NUMBER;
     v_err_rec CSI_DATASTRUCTURES_PUB.TRANSACTION_ERROR_REC;
     v_trx_id number ;
     v_ret varchar2(240);
     v_msg_count number;
     v_msg_data varchar2(2000);
     v_date date;
     t_msg_dummy NUMBER;
     t_output VARCHAR2(2000);
     vl_attribute_id NUMBER;
     v_inst_rec csi_datastructures_pub.instance_rec;
     v_ext_attr csi_datastructures_pub.extend_attrib_values_tbl;
     v_party_tbl csi_datastructures_pub.party_tbl;
     v_account_tbl csi_datastructures_pub.party_account_tbl;
     v_pr_tbl csi_datastructures_pub.pricing_attribs_tbl;
     v_org_as s_tbl csi_datastructures_pub.organization_units_tbl;
     v_asset_as s_tbl csi_datastructures_pub.instance_asset_tbl;
     v_trx csi_datastructures_pub.transaction_rec;
     v_inst_id_lst csi_datastructures_pub.id_tbl;
BEGIN
     APPS.FND_GLOBAL.Apps_Initialize(FND_PROFILE.value('user_id')
,FND_PROFILE.value('resp_id')
,FND_PROFILE.value('resp_appl_id'));
     IF cur_iea_attributes%ISOPEN
     THEN
          CLOSE cur_iea_attributes;
     END IF;
     IF get_trx_id
     THEN
          message('Transaction ID '||to_char(gv_trx_id));
          FOR v_cur_iea_attributes IN cur_iea_attributes
          LOOP
               v_count:=0; -- Initialisation du compteur du ligne. Attention, le nb de lignes dans interface = 14 x nb lignes dans stg
               IF check_unique_serial(v_cur_iea_attributes.numero_serie)
               -- Recuperation de l'item ID
               THEN
                    get_item_id(p_serial_number => v_cur_iea_attributes.numero_serie
                                   ,p_item_id => vl_item_id
                                   ,p_status => vl_status
                    message('Resultat get_item_id: '||to_char(vl_item_id));
                    get_instance_id(p_item_id => vl_item_id
                                        ,p_serial_number => v_cur_iea_attributes.numero_serie
                                        ,p_instance_id => vl_instance_id
                                        ,p_status => vl_status
                    IF vl_status
                    THEN
                         v_trx.TRANSACTION_DATE:=trunc(SYSDATE);
                         v_trx.SOURCE_TRANSACTION_DATE:=trunc(SYSDATE);
                         v_trx.TRANSACTION_TYPE_ID:=gv_trx_id;
                         message('Entrance v_count'||to_char(v_count));
                         v_inst_rec.instance_id:=vl_instance_id;
                         v_inst_rec.object_version_number := 1;
                         IF v_cur_iea_attributes.IAE_GUARANTEE_END_DATE IS NOT NULL
                         THEN
                              v_count:=v_count+1;
                              v_ext_attr(v_count).instance_id := vl_instance_id;
                              message('v_ext_attr(v_count).instance_id: '||to_char(v_ext_attr(v_count).instance_id));
                              message('vl_instance_id: '||to_char(vl_instance_id));
                              get_attribute_id(p_attribute_code =>'GUARANTEE_END_DATE'
                                                  ,p_attribute_id => vl_attribute_id);
                              message('vl_attribute_id: '||to_char(vl_attribute_id));
                              v_ext_attr(v_count).attribute_id := vl_attribute_id;
                              v_ext_attr(v_count).attribute_value := v_cur_iea_attributes.IAE_GUARANTEE_END_DATE ;
                              message('v_cur_iea_attributes.IAE_GUARANTEE_END_DATE: '||v_cur_iea_attributes.IAE_GUARANTEE_END_DATE);
                              message('');
                         END IF;
                         IF v_cur_iea_attributes.IAE_LAST_CTRL_DATE IS NOT NULL
                         THEN
                              v_count:=v_count+1;
                              message('v_count'||to_char(v_count));
                              -- Les 6 champs obligatoires a remplir pour un update
                              v_ext_attr(v_count).instance_id :=vl_instance_id;
                              get_attribute_id(p_attribute_code =>'LAST_CTRL_DATE'
                                                  ,p_attribute_id => vl_attribute_id);
                              v_ext_attr(v_count).attribute_id := vl_attribute_id;
                              v_ext_attr(v_count).attribute_value := v_cur_iea_attributes.IAE_LAST_CTRL_DATE ;
                         END IF;
                         CSI_ITEM_INSTANCE_PUB.update_item_instance
                                   p_api_version => 1
                                   ,p_commit => fnd_api.g_false
                                   ,p_init_msg_list => fnd_api.g_true
                                   ,p_validation_level => fnd_api.g_valid_level_full
                                   ,p_instance_rec => v_inst_rec
                                   ,p_ext_attrib_values_tbl => v_ext_attr
                                   ,p_party_tbl => v_party_tbl
                                   ,p_account_tbl => v_account_tbl
                                   ,p_pricing_attrib_tbl => v_pr_tbl
                                   ,p_org_assignments_tbl => v_org_ass_tbl
                                   ,p_asset_assignment_tbl => v_asset_ass_tbl
                                   ,p_txn_rec => v_trx
                                   ,x_instance_id_lst => v_inst_id_lst
                                   ,x_return_status => v_ret
                                   ,x_msg_count => v_msg_count
                                   ,x_msg_data => v_msg_data
                              -- Output the results
                              if v_msg_count > 0
                              then
                                   for j in 1 .. v_msg_count
                                   loop
                                        fnd_msg_pub.get ( j , FND_API.G_FALSE , v_msg_data , t_msg_dummy );
                                        t_output := ( 'Msg' || To_Char ( j ) || ': ' || v_msg_data );
                                        message( SubStr ( t_output , 1 , 255 ) );
                                   end loop;
                              end if;
                    ELSE
                         message('Update not performed for '||v_cur_iea_attributes.numero_serie||' and '||vl_item_id);
                    END IF;
               ELSE
                    message('Erreur sur '||v_cur_iea_attributes.numero_serie);
               END IF;
               commit;
               message('Commit done for update loop');
          END LOOP;
     ELSE
          message('No Transaction ID - EOP');
     END IF;
EXCEPTION
     WHEN OTHERS
     THEN
          ROLLBACK;
          message('Error in main program, rolling back');
END main;
Thanks!

Todd
The issue seems to because this:
x_instance_rec.inventory_item_id := ib_rec3.inventory_item_id;
You are selecting the item id from your staging table. But the serial number in the csi_item_instances is associated with the instance is a different item id than ib_rec3.inventory_item_id. Hence this error. You cannot change the item in the IB once the instance is created.
You have two choices: comment this out or change the inventory_item_id in staging table to match with the csi_item_instances.
Also a lot depends on what is your serial number uniqueness. If you are using the same serial number for two different items (uniqueness with item_Id) you need to be careful which one you are picking (based on serial number).
Thanks
Nagamohan

Solaris 9 Extended Attributes

Similar Messages

Maybe you are looking for