Best practice for long term maintenance ??

still busy with the long term maintenance requirement.
when maintaining a building my client wants to register the following
- long term maintenance (like 15 till 25 years)
- short term is already in preventive maintenance
- the long term maintenance must be related to specific activitities which contains keyfigures (the keyfigures are obtained from third party libraries which can be used to calculate the estimate cost for a certain acitivity when multiplied with for instance the surface area of the object)
- for the costplanning a report should calculate the estimated costs derived from the keyfigures
- the long term planning should be easy to manage and activities easily be changed in time
is there anything already at hand or an example where long term maintenance like this is implemented ?? I can't see how I can get above requirements in for instance preventive maintenance ??
reward for usefull info
kind regards
arthur

I try to make an config takslist but somehow I can't enter values when I attach the task to a preventive maintenance plan.
I created charateristics and a class with type 300
made a config profile with cu41
I also can't enter values when I attach the general task to a serviceorder
do I still miss something here ??
hmm I made a separete thread for this since it has nothing to do with the initial problem
Message was edited by:
A. de Smidt
Message was edited by:
A. de Smidt

Similar Messages

What is the best media for long-term video storage?

I will be loading several MiniDV tapes into my Mac and want to store the video long-term (in a safe-deposit box). These are going to be home movies with some digital photos or scans as well.
I am curious what folks believe is the best medium for this. I am considering a Passport-style HD like those from LaCie, Western Digital and others. Has anyone had good luck with these? Or am I on the wrong track?
Thank you in advance for your opinions,
jf

I considered getting one of the DVD recorder products from Sony (they say you can plug right into the camera, hit a button and get a DVD copy of the footage in real time)
You understand that a DVD recorder will convert and seriously compress the material in the transcode from DV to mpeg2?
DVDs like this are not a storage system if you are looking to keep original material in a) as close to original quality as possible and b) in an editable format.
40 1 hour DV tapes is just over 500 GB when captured. Get 2 1 TB drives and make two copies of the material. Use one for editing on-line and put the other on a shelf (not in your house). Just be sure to get it back and spin it up every month or so.
The tapes need to be seriously secured. If the safety deposit box is too small, look into a fireproof home vault. 40 tapes do not take up that much space. Just store it in a cool and not humid location.
x

Best media for long term archival purposes?

Browsing the Internet, I have come across several (and partially contradictory) suggestions for the 'best' (longest lasting, with good error correction algorithm, etc.) DVD media. The final conclusion of one of the more competently sounding tutorial (http://adterrasperaspera.com/blog/2006/10/30/how-to-choose-cddvd-archival-media) is: "...So, what am I using? Due to Taiyo Yuden’s superior media quality, and DVD+R’s superior design, I use only Taiyo Yuden DVD+R media. I recommend this media to everyone who wishes to keep their data for a long, long time." Based on the high level of expertise of many users in these forums, I would greatly appreciate any suggestions/comments/references. Thanks, as always, Laci.

Ah! You learn something new every day!
The last time I ordered TY DVDs, they didn't have the silver inkjet printable, only white. Apparently that is something new. Looking again at your links, it *does* say "silver inkjet printable".... very cool.
Now that I'm actually paying attention , I noticed a couple of things: using your link, the "last item" on the page is 8X DVD+R and it does not say "hub printable" (meaning you can print all the way up to the hole).
Not sure what you were looking for, but I know TY has a wider selection of DVD-R than DVD+R.
For example, here's a silver 16X DVD-R hub printable, and it's $38 instead of $46.
http://www.supermediastore.com/product/u/taiyo-yuden-16x-dvd-r-media-silver-inkjet-hub-pri ntable-100-pack?max=30&sortBy=-&search=taiyo+yuden&offset=0&hiddenSearch=+%23Category%3A%2 7DVD-R+Media%27
I've always found it hard finding exactly what I'm looking for with TY, and now it looks even harder since they've added "water shield", "print plus semi-glossy", "hardcoat", but it doesn't look like you can get all of that in one product.
I can't seem to find a "Taiyo Yuden 16X White Inkjet Hub Printable PrintPlus Semi-Glossy Water Shield Hardcoat DVD-R"
Anyway, good discussion. Let us know how the silver inkjet printable DVDs turn out.
BTW, I'm using an Epson Artisan 725 and it's fantastic at DVD (and photo) printing. I was going to get the Artisan 50, too, but found a great sale on the 725.

Best Practices for standardizing long text for EP GUI version

Hello, I have a question that is related to standardizing best practices for all portal applications that use EP
1) The portal team has recommended activating the GUI version from portal to allow the long text to have the same features as the standard GUI. Since this solution is per transaction, we will need to identify what transactions need to have this temporary solution built in. Also, business users will need to remember which transactions they will access via portal or GUI.
(2) Even though the long text function is activated via GUI per transaction, the system will prompt a message of u201CRuntime Error! Program C:\Program Files\Microsoft Office\OFFICE11\WINWORD.EXEu201D. This may create frustrations to the users each time they maintain the long text. The risk of this may be losing the use of long text throughout the maintenance orders, production orders, notifications, material masters, equipment masters, maintenance task lists, production routings, etc.
All feedback welcomed
Thanks Mark

I found the solution, make everything in Illustrator (well text anyway) at a big size then bring it ibto Photoshop in a dicument 1024 x 576 (so no widescreen pixel ratio) then when saving document bring size of Image to 720 x 576 then you get great anti aliased pictures.
Solved.

Noticing a lot of database index fragmentation yet no Health Analyzer alerts...? Best practice for database maintenance in 2013?

Could someone point me to a document for best practices for database maintenance with SharePoint 2013? I have read the 2010 document, but I'm hoping their is an updated one that I'm just missing.
My problem is that our DBA recently noticed that many of our SharePoint databases have high index fragmentation. I have the Health Analyzer rules enabled for index fragmentation and they run daily, but I've never received an alert despite the majority
of our databases having greater than 40% fragmentation and some are even above 95%.
Obviously it has our attention now and we want to get this addressed. My understanding (which I now fear is at best incomplete, more likely just plain wrong) was that a maintenance plan wasn't needed for index fragmentation in 2010/2013 like it was
in 2007.
Thanks,
Troy

It depends. Here are the rules for that job:
Sampled mode
Page count >24 and avg fragmentation in percent >5
Or
Page count >8 avg page space used in percent < fill_factor * 0.9 (Fill Factor in SharePoint 2013 varies from 80 to 100 depending on the index, it is important not to adjust index fill factors)
I have seen cases where the indexes are not automatically managed by the rule and require a manual defragmentation with a Full Scan, instead of Sampled. Once the Full Scan defrag completed, the timer job started handling the index fragmentation automatically.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Best method for converting 8 mm cassettes for long term storage

I have approximately one hundred 8 mm video cassette tapes that I would like to convert to another format for long term storage. I captured my first tape today from my camera Sony DCR VTR 520 which is a digital 8 mm camera. I was not planning to convert the files to DVDs at this time but just keep the avi file on the computer.   The video was just over 2 hours long but the file ends up being 27 GB.   I expecting it to be around 8 GB like a 2 hr DVD but I guess its not the same.
The 8 mm tape I converted was from an very old 8 mm camera which I no longer have (1990). The camera used to capture from is a VTR 520 which is actually a Sony digital 8 mm, which can play back standard 8 mm. I used CS3 on my old computer with standard project settings for DV NTSC 29.97 f/s.   I currently use PE10 so I could use either program.
What do other people use to convert and store videos on??
If I want to keep them as avi files will I have to live with these large file sizes?
I did a search on the forum and found titles that talk about this subject from a couple of years ago but when I click on them they don't come up.   How do you see these older threads?
Any help would be appreciated.

JMJarige,
The only potential problems with this workflow are:
DVR units (I have a Panasonic, but this is pretty much across the board) seldom produce a 100% DVD-compliant disc, and as most add a rudimentary Menu & navigation system to the disc, produce a first VOB (where the Menus & navigation are located), that is tough, if not impossible to directly Import.
In the production to DVD, there is MPEG2 compression applied. If one edits that material, and then they output to any compressed CODEC, the quality loss is easily seen
When I convert from VHS for a client, I create a DVR DVD disc, for their archives (in case the tapes die), but then Capture to DV-AVI to be edited to a DVD-Video. The client gets two sets of discs - one that is produced by the DRV, and then one that is the finished edit of their tapes. For me, it's a two step process, but gives them a backup, plus a finished product.
Good luck,
Hunt

"Best practice" for components calling components on different panels.

I'm very new to Swing. I have been learning from tutorials, but these are always relatively simple interfaces , in which every component and container is initialised and added in the constructor of a main JFrame (extension) object.
I would assume that more complex, real-world examples would have JPanels initialise themselves. For example, I am working on a project in which the JFrame holds multiple JPanels. One of these Panels holds a group of JToggleButtons (grouped in a ButtonGroup). The action event for each button involves calling the repaint method of one of the other Panels.
Obviously, if you initialise everything in the JFrame, you can simply have the ActionListener refer to the other JPanel directly, by making the ActionListener a nested class within the JFrame class. However, I would like the JPanels to initialise their own components, including setting the button actions, by using an extension of class JPanel which includes the ActionListeners as nested classes. Therefore the ActionListener has no direct access to JPanel it needs to repaint.
What, then, is considered "best practice" for allowing these components to interact (not simply in this situation, but more generally)? Should I pass a reference to the JPanel that needs to be repainted to the JPanel that contains the ActionListeners? Should I notify the main JFrame that the Action event has fired, and then have that call "repaint"? Or is there a more common or more correct way of doing this?
Similarly, one of the JPanels needs to use a field belonging to the JFrame that holds it. Should I pass a reference to this object to the JPanel, or should I have the JPanel use "getParent()", or some other method?
I realise there are no concrete answers to this query, but I am wondering whether there are accepted practices for achieving this. My instinct is to simply pass a JPanel reference to the JPanel that needs to call repaint, but I am unsure how extensible this would be, how tightly coupled these classes would become.
Any advice anybody could give me would be much appreciated. Sorry the question is so long-winded. :)

Hello,
nice to get feedback.
I've been looking at a few resources on this issue from my last post. In my application I have been using the Observer and Observable classes to implement the MVC pattern suggested by T.PD.(...)
Two issues (not fatal, but annoying) with this are:
-Observable is a class, not an interface; since most of my Observers already extend JPanel (or some such), I have had to create inner classes.
-If an Observer is observing multiple Observables, it will have to determine which Observer called its update() method (by using reference equality or class comparison or whatever). Again, a very minor issue, but something to keep in mind.I don't deem those issues are minor. The second one in particular, is rather annoying in terms of maintenance ("Err, remind me, which widget is calling this "update()" method?").
In addition to that, the Observable/Observer are legacy non-generified classes, that incurr a loosely-typed approach (the subject and context arguments to the update(Observable subject, Object context) methods give hardly any info in themselves, and they generally have to be cast to provide app-specific information.
Note that the "notification model" from AWT and Swing widgets is not Observer-Observable, but merely EventListener . Although we can only guess what reasons made them develop a specific notification model, I deem this essentially stems from those reasons.
The contrasting appraoches are discussed in this article from Bill Venners: The Event Generator Idiom (http://www.artima.com/designtechniques/eventgenP.html).
N.B.: this article is from a previous-millenary series of "Design Techniques" articles that I found very useful when I learned OO design (GUI or not).
One last nail against the Observer/Observable model: these are general classes that can be used regardless of the context (GUI/non-GUI code), so this makes it easier to forget about Swing threading rules when using them (essentially: is the update method called in the EDT or not).
If anybody has any information on the performance or efficiency of using Observable/ObserverI would be very surprised if this had any performance impact. If it had, that would mean that you have either:
- a lot of widgets that are listening to one another (and then the Mediator pattern is almost a must to structure such entangled dependencies). And even then I don't think there could be any impact below a few thousands widgets.
- expensive or long-running computation in the update methods. That's unrelated to the notification model itself.
- a lot of non-GUI components that use the Observer/Observable to communicate among themselves - all the more risk then, to have a GUI update() called outside the EDT, see remark above.
(or whether there are inbuilt equivalents for Swing components)See discussion above.
As far as your remark 2 goes (if one observer observes more than one subjects, the update() method contains branching logic) : this also occurs with the Event Delegation model indeed: for example, it is quite common that people complain that their actionPerformed() method becomes unwieldy when the same class listens for several JButtons.
The usual advice for this is, use anonymous listeners, each of which handles the event from only one source (and generally very close in code to the definition of that source), and that simply translates the "generic" event notification method into a specific method call of a Controller or Mediator .
Best regards.
J.
Edited by: jduprez on May 9, 2011 10:10 AM

Best practice for distributing/releasing J2EE applications.

Hi All,
We are developing a J2EE application and would like some information on the best
practices to be followed for distributing/releasing J2EE applications, in general.
In particular, the dilemma we have is centered around the generation of stub, skeleton
and additional classes for the application.
Most App. Servers can generate the required classes while deploying the EJBs in the
application i.e. at install time. While some ( BEA Weblogic and IBM Websphere are
two that we are aware of ) allow these classes to be generated before the installation
time and the .ear file containing the additional classes is the one that is uploaded.
For instance, say we have assembled the application "myapp.ear" . There are two ways
in which the classes can be generated. The first is using 'ejbc' ( assume we are
using BEA Weblogic ), which generates the stub, skeleton and additional classes for
the application and returns the file, say, "Deployable_myapp.ear" containing all
the necessary classes and files. This file is the one that is then installed. The
other option is to install the file "myapp.ear" and let the Weblogic App. server
itself, generate the required classes at the installation time.
If the first way, of 'pre-generating' the stubs is followed, does it require us to
separately generate the stubs for each versions of the App. Server that we support
? i.e. if we generate a deployable file having the required classes using the 'ejbc'
of Weblogic Ver5.1, can the same file be installed on Weblogic Ver6.1 or do we
have to generate a separate file?
If the second method, of 'install-time-generation' of stubs is used, what is the
nature/magnitude of the risk that we are taking in terms of the failure of the installation
Any links to useful resources as well as comments/suggestions will be appreciated.
TIA
Regards,
Aasif

Its much easier to distribute schema/data from an older version to a newer one than the other way around. Nearly all SQL Server deployment features supports database version upgrade, and these include the "Copy Database" wizard, BACKUP/RESTORE,
detach/attach, script generation, Microsoft Sync framework, and a few others.
EVEN if you just want to distribute schemas, you may want to distribute the entire database, and then truncate the tables to purge data.
Backing up and restoring your database is by far the most RELIABLE method of distributing it, but it may not be pratical in some cases because you'll need to generate a new backup every time a schema change occurs, but not if you already have an automated
backup/maintenance routine in your environment.
As an alternative, you can Copy Database functionality in SSMS, although it may present itself unstable in some situations, specially if you are distributing across multiple subnets and/or domains. It will also require you to purge data if/when applicable.
Another option is to detach your database, copy its files, and then attach them in both the source and destination instances. It will generate downtime for your detached databases, so there are better methods for distribution available.
And then there is the previously mentioned method of generating scripts for schema, and then using an INSERT statement or the import data wizard available in SSMS (which is very practical and implements a SSIS package internally that can be saved for repeated
executions). Works fine, not as practical as the other options, but is the best way for distributing databases when their version is being downgraded.
With all this said, there is no "best practice" for this. There are multiple features, each offering their own advantages and downfalls which allow them to align to different business requirements.

What are best practice for packaging and deploying j2EE apps to iAS?

We've been running a set of J2EE applications on a pair of iAS SP1b for about a year and it has been quite stable.
Recently however we have had a number of LDAP issues, particularly when registering and unregistering applications (registering ear files sometimes fails 1st time but may work 2nd time). Also We've noticed very occasionally that old versions of classes sometimes find their way onto our machines.
What is considered to be best practice in terms of packaging and deployment, specifically:
1) Packaging - using the deployTool that comes with iAS6 SP1b to package is a big manual task, especially when you have 200+ jsp files. Are people out there using this or are they scripting it with a build tool such as Ant?
2) Deploying an existing application to multiple iAS's. Are you guys unregistering old application then reregistering new application? Are you shutting down iAS whilst doing the deployment?
3) Deploying ear files can take 5 to 10 mins, is this normal?
4) In a clustered scenario where HTTPSession is shared what are the consequences of doing deployments to data stored in session?
thanks in asvance for your replies
Owen

You may want to consider upgrading your application server environment to a newer service pack. There are numerous enhancements involving the deployment tool and run time layout of your application that make clear where you're application is loading its files from.
If you've at a long running application server environment, with lots of deployments under your belt, you might start to notice slow downs in deployment and kjs start time. Generally this is due to garbage collecting in your iAS registry.
You can do several things to resolve this. The most complete solution is to reinstall the application server. This will guarantee a clean ldap registry. Of course you've got to restablish your configurations and redeploy your applications. When done, backup your application server install space with the application server and directory server off. You can use this backup to return to a known configuation at some future time.
For the second method: <B>BE CAREFUL - BACKUP FIRST</B>
There is a more exhaustive solution that involves examining your deployed components to determine the active GUIDS. You then search the NameTrans section of the registry searching for Applogic Servlet *, and Bean * entries that represent your previously deployed components but are represented in the set of deployed GUIDs. Record these older GUIDs, remove them from ClassImp and ClassDef. Finally remove the older entries from NameTrans.
Best practices for deployment depend on your particular environmental needs. Many people utilize ANT as a build tool. In later versions of the application server, complete ANT scripts are included that address compiling, assembly and deployment. Ant 1.4 includes iAS specific targets and general J2EE targets. There are iAS specific targets that can be utilized with the 1.3 version. Specialized build targets are not required however to deploy to iAS.
Newer versions of the deployment tool allow you to specify that JSPs are not to be registered automatically. This can be significant if deployment times lag. Registered JSP's however benefit more fully from the services that iAS offers.
2) In general it is better to undeploy then redeploy. However, if you know that you're not changing GUIDs, recreating an existing application with new GUIDs, or removing registered components, you may avoid the undeploy phase.
If you shut down the KJS processes during deployment you can eliminate some addition workload on the LDAP server which really gets pounded during deployment. This is because the KJS processes detect changes and do registry loads to repopulate their caches. This can happen many times during a deployment and does not provide any benefit.
3) Deploying can be a lengthy process. There have been improvements in that performance from service pack to service pack but unfortunately you wont see dramatic drops in deployment times.
One thing you can do to reduce deployment times is to understand the type of deployment. If you have not manipulated your deployment descriptors in any way, then there is no need to deploy. Simply drop your newer bits in to the run time space of the application server. In later service packs this means exploding the package (ear,war, or jar) in to the appropriate subdirectory of the APPS directory.
4) If you've changed the classes of objects that have been placed in HTTPSession, you may find that you can no longer utilize those objects. For that reason, it is suggested that objects placed in session be kept as simple as possible in order to minimize this effect. In general however, is not a good idea to change a web application during the life span of a session.

Best practice for heirachical data

First off, I have to say that JMX in Java 6 is terrific stuff. Bundling jconsole in with Java has made JMX adoption so much easier for us.
Now, to my question. We have read-only hierarchical data (think a DOM tree) that we would like to publish via JMX. What is the best practice? We see two possibilities:
1. Publish each node of the tree with it's own object name and type. This will allow jconsole to display the information in the tree control.
2. Publish just the root of the tree with an object name and type and then use CompositeType to describe the nodes of the tree. This means you look at the tree in the "Attribute Value" panel of jconsole.
Is there any best practices for such data? We have implemented #2 and it works but we are wondering if long term this might lead to unforeseen consequences.
Thanks in advance.
--Marty

Path,
I did go with #1 and it worked out great. Every node in our tree is an ObjectName node. Works very well for us.
--Marty

Best Practice for Servlets

I guess I'm asking for most peoples' input on what I'm planning to do here ....
Here's what I want to do, and know a bit about.
o I want to make a servlet that serves only XML.
o After that, I want to transform the XML into web pages, RSS feeds etc.. using XSLT.
Here's what I'm not so sure about...
o How should I implement the interface to the web-based aspects? Should the servlet be coded to display HTML pages on "GET" requests? Or should I use a pile of HTML files to make forms?
o What do I use to perform the XSLT transformations? Where should the set of solutions be placed relative to my servlet? Would a user then access this solution rather than the servlet itself?
o How do I code the servlet on one machine, and then test it on another without breaking the libraries? How do I set up any libraries I might have to use (like for XSLT transformations) on the server?
Any other advice here? I'm sure this is done often, but I can't find a resource that explains the best practices for it all.
I know this sounds like a lot of stupid questions. I've had lots of programs working with Java before, but I'm at a loss as to how I'm supposed to package libraries I use in my programs - moreso with a servlet. To make matters worse, I plan on using MySQL as the database.
If there's some wizard on the forums here who's willing to say more than just "RTFM" (of which there is none to answer my questions together as one), I'd be very very happy ":^)

Let me re-pose my question so as to be specific
enough to not be picked apart in my answer.
I want to FIRST AND FOREMOST, create a servlet that
serves up XML based on parameters given to it (how?
who cares.).What does "serves up XML" mean?
Let's be precise. Do you intend the servlet to send the XML back to the client? Or is the XML an intermediate step in your processing? (Yes, it matters.)
Then, I want to create interfaces (HTML, RSS,
boogledeedoo) to this XML data by having either JSP,
another servlet or insert something else here,
transform the XML into whatever the desired format
is."interface" is a loaded term in Java. What do you mean by it?
>
My assumption is that I'll make the servlet that is
capable of outputting my desired XML data and then
create another servlet that will poke it for data as
needed to transform the XML into HTML. This servlet
would also likely serve as the web site itself and
would manage user logins etc...(persistance yaddy
yadda)You're not thinking about this properly.
"yadda yadda" == muddled thinking.
My other assumption is that I'll make another servlet
that will poke the XML servlet and transform that
into RSS or anything else I can dream up.How does "poke the XML servlet" fit into the request/response protocol that is HTTP? Please explain.
-=-!REASONING!-=-
Previously, when I was working with PHP, I liked to
make scripts that would display interfaces and post
to themselves. OK, now I see. "interface" == GUI in a browser to you. Very good.
You can create a JSP that is an interface. You can have that JSP submit the HTTP POST or GET request to itself. No problem there, as long as "itself" knows what to do with the request.
It was a nice way of creating a
complete little package. Everything for one function
was encapsulated nicely under one roof. No excessive
HTML files all over the place to nurture.A simple problem, a simple solution. You can do that with a JSP.
Look. Part of my inability to describe this well is
because I DO feel like I'm in a lot of directions at
once. Or you don't understand the technology very well.
But I have to be in order to pull together
some sort of plan for myself. I understand many
concepts and have just finished studying object
oriented design etc..."Just finished"? How long did it take?
I know things about how Tomcat does connection
pooling for SQL connections.Great. Not much to understand there. It's harder to figure out how to do n-tier apps with more than one page well.
I do know how to use Google, probably a lot better
than most. But rest assured, I've yet to find a
little guide as complete as any of the "LAMP" books
there are out there. Which by the way, I have never
purchased.That's because Java Enterprise Edition isn't intended for little problems. LAMP is. Maybe the limitation is that you are used to "little" problems and not bigger ones.
If JEE seems scattered and complex, it's because it is. It encompasses more than LAMP.
I'm confident in good guidance, and not a heartfelt
smackdown. I'm still waiting for some clear suggestions.I gave you one, you just didn't know it: go read about Spring.
http://www.springframework.org
It'll help you structure complex apps from the user interface to the database in the back.
You're welcome.
%

ECATT: SAP's Best Practice For eCATT

Hello All,
If multiple projects are handled on same server, then the master data keep on changing due to which the screen sequences of transactions may change and hence causing the failure of earlier automated eCATT scripts.
What is the best practice recommended by SAP for such situation both in long term as well as short term considering project deadlines?
Thanks & Regards.

Hi SAP Developer,
as far as I know there are no best practice guides for that from SAP.
But from common experience in automating testing one can propose:
For long term:
- organize your processes to be tested aligned as a number of szenarios; do a test case design also incorporating test data to be used; on that base derive (master) data that can be used in common by all szenarios; all other data should be used from single szenarios exclusively;
- use scripts also for creation of (master) data;
- try to use internal number assignment or create numbers in your eCATT script, so that every process run uses new new data accroding it's needs
- try to check customizing using CHETAB or BC Sets, stop the process if important settings are not there
The target of all this is to ensure, that neither customizing nor master data properties can raise different screen sequences.
Another option is to make your scripts more flexible regarding 'small' sequence changes like upcomming popups etc. when using SAPGUI command. This can be achieved by setting the 'Active' option of 'ProcessedScreen' elements.
If you use 'O' like optional, eCATT will only process the ProcessedScreen branch if the programm and dynpro number are matching the screen currently shown by SAP Gui.
Hope I could help a bit.
Best regards
Jens

Best practices in Queue table maintenance

Hi Fellow AQ Users,
I am looking to hear from the community about best practices in queue table maintenance.
I have been mining through metalink about various Oracle recommendations and putting
together a set of recommendations as a starting point for my DBAs.
I am looking to answer questions like these --
How often (in relation to messaging load) would you coalesce and rebuild the indexes?
How often would you rebuild the table itself to get rid of the high water mark issues ?
and what procedure would you use to do that?
Would really love to learn from your experiences in this area. We are using 9.2.0.7
64 bit DB and have plans to go to 10g over the next year. So, I am looking at 9i related
stuff and then 10g.
Thanks
Vijay

Hello,
In general you coalesce once per day ideally during a quiet time to avoid ORA-54 errors as per <Note:271855.1>. Some customers do it more often than that but once per day is a good starting point.
In terms of shrinking the queue tables you can use the procedure in <Note:304522.1> with a null 3rd parameter. This is an offline procedure so you could only run it during a maintenance window. In 10.2 onwards you can dynamically shrink the queue table and IOTS. Again it depends on exactly what you are doing with your queue tables how often you might need to do this.
Thanks
Peter

Microsoft best practices for patching a Cluster server

Good morning! I was wondering if you had any web resources (Webcasts) or whitepapers on Microsoft best practices for patching a Cluster server? I will list what I seen online; the third one was very good:
Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster
http://technet.microsoft.com/en-us/library/cc731844(v=ws.10).aspx
Failover Clusters in Windows Server 2008 R2
http://technet.microsoft.com/en-us/library/ff182338(v=ws.10)
Patching Windows Server Failover Clusters
http://support.microsoft.com/kb/174799/i

Hi Vincent!
I assume this step-by-step guide can also be used if you have more then 2 nodes, as long as you make sure majority of nodes are up (and quorum disk is available).
I just had a strange experience during maintenance of 2 nodes (node nr 7 and nr 8) in a 8 node hyper-v cluster R2 SP1 with CSV. I used SCVMM2012 to put the nodes in maintenance mode. (live migrating all resources to other nodes.) I then look in "Failover cluster
manager" to check that the nodes had been "Paused". And yes everything was just fine. I then did windows update and restartet, no problem. But after restart I wanted to run PSP (HP's update utility) to update some more drivers,software etc. During this PSP
update, node nr 02 suddenly failed. This node is not even a HP Blade, so I'm not sure how, but I know network NIC drivers and software where updated from PSP. So my question is:
Does changes in "Network Connections" on nodes in "Pause" mode affect other nodes in the cluster?
The network are listed as "Up" during Pause mode, so the only thing I could think of is that during PSPs driver/software update, NICs on node 07 and 08 were going down and up differently somehow making Node 02 fail.
So now during maintenance (Vendor driver/software/firmware updates, not MS Patches) I first put the node in "Pause" mode then I stop cluster service, (and change it to disabled) making sure nothing can affect the cluster.
Anders

Best-practice for Catalog Views ? :|

Hello community,
A best practice question:
The situtation: I have several product categories (110), several items in those categories (4000) and 300 end-users. I would like to know which is the best practice for segment the catalog. I mean, some users should only see categories 10,20 & 30. Other users only category 80, etc. The problem is how can I implement this ?
My first idea is:
1. Create 110 Procurement Catalogs (1 for every prod.category). Each catalog should contain only its product category.
2. Assign in my Org Model, in a user-level all the "catalogs" that the user should access.
Do you have any idea in order to improve this ?
Saludos desde Mexico,
Diego

Hi,
Your way of doing will work, but you'll get maintenance issues (to many catalogs, and catalog link to maintain for each user).
The other way is to built your views in CCM, and assign these views to the users, either on the roles (PFCG) or on the user (SU01). The problem is that with CCM 1.0 this is limitated, cause you'll have to assign one by one the items to each view (no dynamic or mass processes), it has been enhanced in CCM 2.0.
My advice:
-Challenge your customer about views, and try to limit the number of views, with for example strategic and non strategic
-With CCM 1.0 stick to the procurement catalogs, or implement BADIs to assign items to the views (I experienced it, it works, but is quite difficult), but with a limitated number of views
Good luck.
Vadim

Best practice for long term maintenance ??

Similar Messages

Maybe you are looking for