Dealing with Latches issues

Question

Working on 10g R2/windows
I had the following issues.
script 1:
script used to get this output:
select name, gets, sleeps,
sleeps*100/sum(sleeps) over() sleep_pct, sleeps*100/gets sleep_rate
from v$latch where gets>0
order by sleeps desc;
output from script 1
NAME GETS SLEEPS SLEEP_PCT SLEEP_RATE
library cache 142095179 3166 79.2292292 .002228084
shared pool 55364580 472 11.8118118 .000852531
slave class create 2123 248 6.20620621 11.6815827
QUESTIONS
Q1:
Looking at this output we can suppose that the system is suffering from library and shared pool latches? If we rely on SLEEP_PCT column
OR
Q2
the system is suffering from the slave class create latch? is we rely on SLEEP_RATE?
script 2
SELECT event, time_waited,
round(time_waited*100/ SUM (time_waited) OVER(),2) wait_pct
FROM (SELECT event, time_waited
FROM v$system_event
WHERE event NOT IN
('Null event',
'client message',
'rdbms ipc reply',
'smon timer',
'rdbms ipc message',
'PX Idle Wait',
'PL/SQL lock timer',
'file open',
'pmon timer',
'WMON goes to sleep',
'virtual circuit status',
'dispatcher timer',
'SQL*Net message from client',
'parallel query dequeue wait',
'pipe get'
) UNION
(SELECT NAME, VALUE
FROM v$sysstat
WHERE NAME LIKE 'CPU used when call started'))
ORDER BY 2 DESC;
output from script2
VENT TIME_WAITED WAIT_PCT
Streams AQ: qmn coordinator idle wait 89454826 41.19
Streams AQ: qmn slave idle wait 89453935 41.19
Streams AQ: waiting for time management or cleanup tasks 31961187 14.72
jobq slave wait 3172020 1.46
CPU used when call started 1856726 .85
db file sequential read 700713 .32
class slave wait 263571 .12
Thanks for your clarification

Answer 1

I think you can safely assume that you know nothing of substance.
Numbers are only numbers unless they have a context. Is a query that takes 0.5 seconds fast or slow? It depends. Same thing here.
Without knowing whether response times are acceptable or not no comment is possible.
Without knowing whether this is an improvement no comment is possible.
Without knowing if there are new issues no comment is possible.
PS: In the future please post the entire version number and format your code with PRE tags as described in the online FAQ.