Monday Mar 10, 2014

ORAchk Health Checks for the Oracle Stack

ORAchk includes EXAchk’s functionality and replaces the popular RACcheck tool, extending the coverage based on prioritization of top issues reported by users, to proactively scan for known problems within:

  • E-Business Suite Financials Accounts Payables
  • Oracle Database
  • Sun Systems

ORAchk features:

  • Proactively scans for the most impactful known problems across your entire Engineered System as well as various layers of your stack
  • Simplifies and streamlines how to investigate and analyze which known issues present a risk to you
  • Lightweight tool runs within your environment; no data will be sent to Oracle
  • High level reports show your system health risks with the ability to drill down into specific problems and understand their resolutions
  • Can be configured to send email notifications when it detects problems
  • Collection Manager, a companion Application Express web app, provides a single dashboard view of collections across your entire enterprise

ORAchk will expand in the future with more high impact checks in existing and additional product areas. If you have particular checks or product areas you would like to see covered, please post suggestions in the ORAchk community thread accessed from the support tab on the document below.

For more details about ORAchk see Document 1268927.1

Monday Mar 03, 2014

Join the Oracle Support Customer Advisory Program

Untitled Document

GPIcon

Oracle Support values your involvement and input, especially on the tools and features that help you use our software or hardware products more effectively.

You can now opt in to the Oracle Support Customer Advisory Program and become part of the feedback process for these Oracle Support tools. Tell us about yourself; let us know that you would like to provide feedback, and which areas of focus that most interest you.

We may ask you to provide input through various forms of engagement: one-on-one session, small group discussion, etc. By contributing your thoughts and ideas, you have the opportunity to help influence new and existing Oracle Support products—and get a first look at new designs and features before general availability. You may also have the chance to join us in testing.

We look forward to collaborating with you.

Monday Jul 11, 2011

Use of WGET instead of downloading patches and software "manually"

-- Update July 11st, 2011 --

Use of LANG=C is now included in the scripts.

On servers where the locale is not english, the use of grep may have unintended side effects.  The script now sets this to avoid issues with customers on non-English servers.

We broke WGET for Patch Downloads.  This is NOW FIXED.

Thanks to some customers for reporting this we now know the problem and the solution.

When you see examples like this

$WGET  --load-cookies=$COOKIE_FILE --save-cookies=$COOKIE_FILE --keep-session-cookies "https://updates.oracle.com/Orion/Services/download/p8534378_111060_Linux-x86-64.zip?aru=11399081&patch_file=p8534378_111060_Linux-x86-64.zip" -O $OUTPUT_DIR/p8534378_111060_Linux-x86-64.zip   >> $LOGFILE 2>&1

you will now see

$WGET  --user-agent="Mozilla/5.0" --load-cookies=$COOKIE_FILE --save-cookies=$COOKIE_FILE --keep-session-cookies "https://updates.oracle.com/Orion/Services/download/p8534378_111060_Linux-x86-64.zip?aru=11399081&patch_file=p8534378_111060_Linux-x86-64.zip" -O $OUTPUT_DIR/p8534378_111060_Linux-x86-64.zip   >> $LOGFILE 2>&1


I am so sorry you have this issue. Let me know if you see it fixed in production!

----

As some of you know FTP for downloading patches went away. :-<

And as some of you might not know WGET was put in place to allow for the same access but via the security mechanisms used by Oracle.

We are working on allowing a hybrid approach to downloads via My Oracle Support.
You search and collect up what you want in My Oracle Support, but instead of downloading to your desktop (which you then might need to copy over to a server), you can copy a WGET script complete with authentication token to use directly say a unix box of your choosing (could even be an Enterprise Manager repository or staging server you defined) to get the large files.

In process for a forthcoming release (can't mention dates, releases, etc....) we want a little feedback from you.

And so you know this ALSO can include software upgrades and base software (something which is rather large depending on the product - like 10 to 80 gig!).


My question for those who use WGET....

Would you copy a script to your clipboard from say My Oracle Support (and paste into your own .sh type script which you have open in a terminal session?)
or maybe just want to copy the file to your desktop or mounted drive?
What . (dot) format would you expect the file to be in?

Any other tips or tricks you might offer for doing this kind of interaction?

See the image below for an "idea" of what we are talking about - once you have selected a list of patches and were given something like this...

What is your feedback?

-- Update July 7th - here are some updated examples of the dialog box.

Feedback, so far, indicates just the download .sh button would be probably enough.

wget more2.jpg

--- Update.....
Here is a copy of the .sh file... still a work in progress.
We hear you about Proxy setting. Will work to get that as part of this.
Will work to make it more "user readable"...

#/bin/sh

# # Generated Tue Jun 01 06:48:48 PDT 2010 # Start of user configurable variables #

# Path to wget command WGET=/usr/bin/wget

# Location of cookie file COOKIE_FILE=/tmp/$$.cookies

# Log directory and file

LOGDIR=/tmp LOGFILE=$LOGDIR/wgetlog-`date +%m-%d-%y-%H:%M`.log

# SSO username and password SSO_USERNAME=your.name@oracle.com SSO_PASSWORD=

# E-Delivery token

# The EPD_TOKEN will expire 48 hours after the following generation date # 2010-06-01 10:03:29 UTC EPD_TOKEN=ZjJQSFlNblZjcTRIaXYvNHFQWUVjUSBFUEQtZGlhcm11aWQuY2F3bGV5QG9yYWNsZS5jb20gMjI4NzUyMCBXZWxjb21lUGFnZSA4NDAgMTI3NTQxNTQwOQ@@

PASSWORD_9434145=

# # End of user configurable variable #

if [ "$PASSWORD_9434145 " = " " ]

then echo "Please edit script and set PASSWORD_9434145" exit fi

if [ "$SSO_PASSWORD " = " " ] then echo "Please edit script and set SSO_PASSWORD" exit fi

# Contact updates site so that we can get SSO Params for logging in SSO_RESPONSE=`$WGET http://updatesdemo.us.oracle.com/Orion/Services/download 2>&1|grep Location`

# Extract request parameters for SSO SSO_TOKEN=`echo $SSO_RESPONSE| cut -d '=' -f 2|cut -d ' ' -f 1` SSO_SERVER=`echo $SSO_RESPONSE| cut -d ' ' -f 2|cut -d 'p' -f 1,2` SSO_AUTH_URL=sso/auth AUTH_DATA="ssousername=$SSO_USERNAME&password=$SSO_PASSWORD&site2pstoretoken=$SSO_TOKEN"

$WGET --post-data $AUTH_DATA --save-cookies=$COOKIE_FILE --keep-session-cookies $SSO_SERVER$SSO_AUTH_URL >>

$LOGFILE 2>&1$WGET --load-cookies=$COOKIE_FILE --save-cookies=$COOKIE_FILE --keep-session-cookies

"http://updatesdemo.us.oracle.com/Orion/Services/download/p9434145_11107_Solaris-64.zip?aru=12254122

&patch_file=p9434145_11107_Solaris-64.zip&patch_password=$PASSWORD_9434145" -O 9434145_file_1 >> $LOGFILE 2>&1

$WGET --load-cookies=$COOKIE_FILE --save-cookies=$COOKIE_FILE --keep-session-cookies "http://updatesdemo.us.oracle.com/Orion/Services/download/p8705958_10204_Linux-x86.zip?aru=11799041 &patch_file=p8705958_10204_Linux-x86.zip" -O 8705958_file_1 >> $LOGFILE 2>&1

$WGET --load-cookies=$COOKIE_FILE --save-cookies=$COOKIE_FILE --keep-session-cookies

"http://epd-demo.us.oracle.com/EPD/Download/process_download/A89130-01.zip?file_id=4462918&aru=4985314

&userid=your.name@company.com&egroup_aru_number=10615835&email=your.name@company.com&country_id=840

&patch_file=A89130-01.zip&userid=your.name@company.com&email=your.name@company.com&country_id=840&token=$EPD_TOKEN" >>

$LOGFILE 2>&1

# Cleanup rm -f $COOKIE_FILE


Tuesday Dec 21, 2010

My Oracle Support: Your Mobile Needs

We know you have issues with My Oracle Support. But one area which we haven't tried to help customers is in the mobile space.

If you have a few minutes GET INVOLVED!
Our goal is to be able to deliver a "5 star" solution via mobile for limited set of specific and important uses. We don't plan on delivering the kitchen sink. Help us plan on what is REALLY important to you when on the move.

We will be posting not just a new survey, but a "presentation" which you can view from your smart phone or browser giving you a look into where we are going AND it allows you to provide feedback on each and every thing we are doing. Crazy right? We want to hear in great detail what you think about what we plan to do, so when we do it, it can be just what you need to do your job. Stand by!

Thursday Oct 22, 2009

Part One: Gathering Feedback from Recent Usability Research and Studies

Back to Summary

The design team for My Oracle Support reaches out to customers with design issues and new designs on a regular basis. Of course, we only see a limited number of users during any testing or survey work despite the many tens of thousands of folks out there,. To help us understand a full range of customer requirements, we try to solicit input from a mix of customers: Large customers (those with dozens of Oracle administrators), small customers (even down to a shop with one or two Oracle administrators); educational, national and international businesses; customers who use the configuration manager, and those who do not. Till now, we have not focused on "new" My Oracle Support customers. Although, I think this would also yield interesting results. I won't try to define "administrators" here, but I suspect you are one if you use My Oracle Support.
We interact with customers in a few different ways, and via these processes generate new designs, issue lists or requirements, which in turn are given to a UI designer (usually me) to design. We prioritize the features or changes and give them to development to implement. Not all changes go through designers. Some go directly to development. Sometimes that can be ok, but generally with design issues we try to follow one process.
We gather the feedback in 3 basic ways: View your feedback from the site, from surveys, and from interviews. Generally all of these methods tend to result in additional e-mail, and sometimes we send customers prototype screenshots to check that we are doing the right thing. I am primarily going to cover the customer interviews in this post. But let me quickly address the other two feedback methods.

Feedback
Your feedback via the UI (the link the top right corner) is reviewed, categorized, and makes its way into enhancement requests and bug fixes. The team that reviews them does a great job of reading and organizing all of your feedback. Here is a recent item,

 

"Hi, after leaving My Oracle Support open over night (which of course I shouldn't have done in the first place), I got the error message "A server connection error occurred. IO Error Error #2032 Please try again later" I would have expected something like "You have been logged out due to inactivity" or the like. Can you please research/comment? Thanks"

 

Well that particular comment is a good one, and one that is still relevant today--I am NOT a fan of the Error #2032. But try to figure out by reading the whole post why this is not a usability priority (and then post your thoughts on it!). About 150 of these feedback messages are received each week. Let me break down the recent feedback. User Administration issues (18.5%), General Usability issues (15%), Managing Service Requests (7%), Support Identifier issues (6%), Creating a Service Request (6%), "You stink" issues (6%) and other smaller areas of feedback. This covers features like adding new administrators, adding/removing permissions, search results quality, registration issues, general bugs and yes... performance. Performance is near and dear to a lot of people's hearts, and I think it was Dan Rosenberg who coined, "there is no such thing as a slow usable interface". So let me just say that performance is on everyone's mind, including the design team. We will cover performance issues in Part Three. Hopefully addressing customer complaints like this,

 

"I have never used something so slow and it is extremely cumbersome to navigate. It takes forever for the main screen to load. I don't understand what could be going on in the background. As a DBA of 20 years, I can say without a doubt this will be the last time I look to your website for anything except the expected worse than normal, painful experience of creating a TAR in the new system."

 

Ouch, but sometimes the truth hurts. But we do hear you and are working to improve performance and improve the ability to create a Service Request (a TAR, for you old timers).

Surveys
A variety of surveys are conducted including the usability survey which was linked from the Getting Started region (now available only from the sign-in page). I have also sent out other surveys to as many as 8000 participants covering issues like patch process, creation of patch plans and "carts" of patches, key feature needs and requirements, and general survey stuff like how many folks work on your team, etc... This information is used to help set priorities, define who our users are (you!) and what their typical roles and responsibilities are within their organizations. It is also a good place to find folks for our one-on-one interviews. These results get processed typically into high-level design goals and directions, aka, Improve SR Flow, Improve Help). Typically a survey uncovers very few specific issues.

Interviews
When we interview customers, it typically follows a basic model. We spend half of the time listening to the customer about their needs. Typically this is specific to a single issue like patching, or providing proactive health checks. Then, depending on when we are speaking to the customer (early during requirements gathering, during design, or during early development), we show flow diagrams, mockups, or even some working code. With mockups or working code the customer drives the UI, and interacts with it. We tend to give little or no instruction or hints. We watch where and how the UI functions, where it breaks, or helps the customer. We typically do a final round of sessions with about 6 customers working with close to final code. While with early sessions were for formulating what we should build, in the later sessions we are focused on design issues of what we have built. If we find major missing functionality that typically goes into a bucket for future releases.

Issues are found in a few ways;


  1. The customer explicitly tells us (i.e., "I don't know what 'Suppression' means")

  2. The customer implicitly tells us (we watch their cursor move around and around never landing on the button we think they should use, i.e., it is not obvious, in the right location or labeled correctly)

  3. The designer, a Product Manager, or developer makes a note of something they notice

  4. The product does something "silly", and we note it and work around it during the session.


These issues can be at the highest level (are the concepts correct?), down to the nitty gritty (is the icon too small, poor grammar, or bad layout?). We document every issue and prioritize them with the Oracle support product managers.

 

Let me tell you how I prioritize this feedback. I follow a model similar to something I learned from the great designer, Phil Haine. Although we have not applied this model directly, I use to do my own prioritization of bugs. Try this... Rank each usability issue by the follow questions and multiply the results together to get the UI score.

How Many Users Does it Impact (3 - All, 2 - Some, 1 - A few or a Limited User Role)
How Bad is the Problem (4 - Severe, 3 - Critical, 2 - Important, 1 - Not Important)
How Often Does it Occur (3 - All of the Time, 2 - Some of the Time, 1 - Infrequently)

I think you might find this interesting because it might help you realize how we have to determine what is best for everyone. For example, if you file a bug against the customer user administrator feature, you might consider it the most important, but there might be a bug in knowledge searching, and that could take priority based on this model (because more users are impacted more often).

Let's take a look at some real bugs from customers and how this model helps us prioritize (and makes for a good conversation in our blog). I have already sorted them by most to least important, and have associated a development effort with each. The development effort is both for the design and development of the fix. "High" generally is something which requires many days to fix, maybe requiring multiple people and impacts more than just the user interface. Medium could require a day or more, while Low is typically a few hours' worth of work. Very Low (VH) is trivial to fix. This does not include QA time, changes to help or marketing materials. These are real issues found in the last release.

 


























































































Sample (Real) Issue

# Users

Bad

Often

Total

Dev


1. The Browser Back button does not take you "Back"

3

4

3

36

H


2. Text: "Run" should be called "Search" in toolbar

3

2

3

18

VL


3. Can't submit a search by pressing return in a field

3

2

3

18

L


4. Vertical Scroll bar is missing from Patch Recommendations

2

3

3

18

M


5. "Enterprise Patch Recommendations" is confusing term

2

2

3

12

VL


6. Deploy column (in Patch Plans) is not sorting correctly

2

2

3

12

M


7. No way to select all language packs you need for an EBS patch

2

2

3

12

M


8. Download Text and number should align correctly

3

1

3

9

VL


9. Download Trend for Patch Downloads has no labels

2

2

2

8

L


10. Task Region cannot be dragged onto the screen when empty

1

2

3

6

M

 

This list is just to give us a discussion point. In Part Two of this article, I will provide a richer set of feedback from customers and discuss how we resolve these issues.
Let me explain some of these issues for those who don't want to wait till Part Three. And it makes the point of how we prioritize usability issues. Everyone uses the browser's Back button. So even as a flash "application" we saw ourselves and eventually customers blowing away the flash app and returning to their previous HTML page. So from the beginning we created markers that the browser would detect, so that Back would take the user back to the previous screen in our application. That is, going from the Dashboard to the Knowledge page and then 'Back' would return the user to the Dashboard. So fixing these issues has always been important. I think there are still places (like in the SR wizard, where going 'back' does not go back one step in the Wizard, but goes to the page before the Wizard) we need to fix that so that 'Back' always means back one page.

We didn't provide a good answer to the back button question with pages like Knowledge where the search results morph into a master/detail view (with the list of articles on the left and the articles details on the right). This was done so you can quickly scan a large chunk of articles without excessive navigation. But then what does "Back" mean? One can click Article A, then B, then C without any other navigation. But what happens with "Back"? Should "Back" go back to Article B then A? Or should it go back to the full view of Articles? Let us know what you think (I have thoughts on this. ;->) So "Back" is at the top of our list and continues to be an issue as we develop new features. We haven't found a single solution which can fix this problem.

One more example: the vertical scroll bar missing from a table. If you have a table with a lot of data you darn well need a scroll bar, right? So how can this not be a 4x3x3, a top priority? Because not all customers use the configuration manager, and not all targets have recommendations yet. So if you are an EBS user, or an organization that doesn't use configuration manager, you would not be impacted by this issue. So even though it is a real problem (one that is now fixed), it was not ranked at the top.

You can also see that there is the factor of development effort. The closer we are to a release, the tougher it is to make big changes. Even as a designer I understand this. Making even late binding design changes can sometimes cause unintended consequences--Maybe we forgot about some error condition, or a set of permissions which could impact users. So we try to make sure that the bigger, more troubling important items get worked sooner in the development cycle. Towards the end of the cycle we can typically knock out the very low (VL) items with little impact. So the sooner we get customer feedback the more opportunity we have fix issues prior to shipping.
So now you have some idea of how we go about the process of listening and cataloging issue. You probably want to know more about what we have heard from customers like you. We will cover that in Part Two. Stay tuned!

P.S. Recall the Error #2032 error earlier in the post? Did you score it? I scored it at 2x2x1 because it happens when you leave you session overnight and it doesn't really do anything surprising (the session times out). But, duh, the message should be better and likely just return you to the sign in page to sign in again. And yes, that same error is a catch all for some other conditions; I am just talking about this one. I filed a bug to fix that. Thanks to the customer who filed it.


Next: Part Two: Actual User Feedback
Part Three: Special Areas of Feedback: Content, Quality, and Performance

 

Monday Sep 07, 2009

Fruits of our Labor (Holiday Edition)

Labor Day (celebrated today in the US) celebrates workers and originated with the Nine-Hour Movement in Canada (similar to the International Workers Day, or "May Day").

However, it's a well-known fact that IT and business technology professionals anywhere in the world often have schedules that don't exactly fit the 9am to 5pm professional standard since problems can - and do - arise out of anywhere, anytime.

This being the blog for My Oracle Support, it should be no surprise that our most recent release of My Oracle Support is aimed at simplifying how you approach those problems and enabling more and more of our customers to tackle issues as fast as possible (or even before they happen).

So, if you haven't already, we encourage you to check-out Tony's recent blog post, the My Oracle Support Welcome Center (Note 873313.1), and continue asking your questions and sharing your thoughts here and in the Using My Oracle Support Community....

For those of you taking a well-deserved day off in the US - we encourage you to enjoy it!

Tuesday Sep 30, 2008

Comments now working

[Read More]

Wednesday Mar 19, 2008

Customizing your region columns

[Read More]
About

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
5
6
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today